Hi, > Could you please show us where this “standard release process” is documented, > and explain how we are somehow deferring from this “standard”?
The process is described here [1] which references [2] and best practise described here [3] and there is a work in progress with clearer MUSTs and SHOULDs in it. (I was unable to find the link) In short the normal process is to have one or more RCs each tagged in version control and placed on dist.apache.org along with a VOTE and a DISCUSS thread for each RC. The RM keeps making release candidates and putting them up for vote and discussion to the PMC until one gets the required 3 +1 binding votes (and more +1 than -1 votes). The RC is then moved to the release area and the release announced. Several bits of the noRC/lessRC (as described) deviate from this standard process, most of the deviations are minor (ie single discuss thread for all RCs), testing a nightly rather than the RC itself, but others are not ie the apparent need to build consensus before making a RC and calling for a vote. The later may be a misunderstanding of the then undocumented noRC process on my part, but that's what happened with the TourDeFlex release. With few PMC members voting a single -1 or indication that that how someone will vote can basically acts as a veto. Thanks, Justin 1. http://www.apache.org/dev/release-publishing.html 2. http://www.apache.org/foundation/voting.html 3. http://incubator.apache.org/guides/releasemanagement.html
