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

Reply via email to