build tooling release consequences

[Marshall Schor <ms...@schor.com>]

Hi everyone,

Just a reminder - whenever some build tooling is released, the normal sequence 
of things is:


1) a snapshot "deploy" to repository.apache.org is done prior to the creation of 
the release.  This allows people to continue to depend on the snapshot at its 
latest level.

2) the release is posted for review, and voted on.  Then the "release" button is 
pushed (if the vote passes).  This causes the release artifacts in the staging 
repository to be uploaded to Maven Central.

3) Sometime after the release has been uploaded, the deployed snapshot is 
automatically "cleaned up" (that is, deleted) by the Nexus.



Because of (3), after the release happens, any poms that depend on the snapshot 
versions of the build tooling need to be updated to the release versions so they 
can continue to build.

-Marshall