Ugh, somehow we all missed the fact that there aren’t Apache headers on assembly/assemble*.xml. Can anyone think of a way we can make an exception? Are they auto-generated? Did they come from somewhere else? Do the lack any creativity? Otherwise we have to roll an RC3. I checked in Apache headers on those files.
And if we do make an RC3, I also fixed a couple of minor nits in the README and RELEASE_NOTES. Thoughts? -Alex On 11/16/14, 1:47 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Hi, > > >so I learned a lot more this time. > >First of all: If you follow the normal release path of "mvn >release:prepare" "mvn release:perform" the tags arent created correctly. >You have to set the version to the release version and set the tag >property manually, commit and tag that commit manually. After that a "mvn >-P apache-release deploy" has to be issued to stage the release >candidate. As soon as that was successfully, update the version to the >next development version and set the tag back to HEAD. (I just thught I'd >post that for documenting it) > >Also I left the staging repo open the last time. This time I closed it >which makes Nexus do all sorts of PGP checks as well as checks if the >poms respect the apache release policy and all mandatory fields contain >valid values. After the repo is closed you actually get a public url for >testing the RC: > > >https://repository.apache.org/content/repositories/orgapacheflex-1001? > > >Think with this it's a lot easier to check. > > >Chris
