Page History

...

Send a short e-mail to dev@struts.a.o informing about the new packages and to give people enough time to test the distribution (actual bits). Wait around a week before posting Vote. If no show-stoppers reported, start a vote thread for build quality designation.

Clean up repository

It doesn't matter if the bits will be accepted or not, development continues  Switch to release/X.X.X.X branch and execute the below command:

git flow release finish -n X.X.X.X

-n option is need to avoid tagging the release, the Maven Release plugin did that already. If the release branch was published to the remote it won't be deleted locally, it must be done manually after removing branch from the remote:

git push --delete origin release/X.X.X.X

This will remove the branch from the remote, now we can merge once more the release branch (when on develop) and remove it

git merge --no-ff release/X.X.X.X
git branch -d release/X.X.X.X

Now both master and develop branches should be up to date with the changes introduced by the release.

Vote on it

Post a release/quality vote to the dev list (and only the dev list). The example mail is on Sample announcements page.
If the vote result is for an ASF release (i.e. not test build), update site, announce. If the vote result is for GA, push to central.

...