There was a bit of discussion in the Maven BoF last week at Community Over Code on the topic of parent POM release processes. This was a follow up to a thread on the board mailing list in September "RFC: Releasing with lazy consensus".
TL;DR A few different projects have not been voting on parent pom releases, and the debate was is this allowed. I haven't seen a formal decision on the topic, but the consensus at the BoF was that a vote is required when releasing a parent pom. (Personally I have mixed feelings about this, I can see both sides of this debate) There was a recommendation to ease some of the burden/toil of this extra release step, stage parent pom release and project release at the same time, e.g.: 1. Stage the parent pom release (up to step 4 in: https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy ) 2. Stage the sub-project 3. Call for a single vote containing the parent and sub-project. 4. Release staging repos (and move both artifacts to dist.apache.org) 5. Other release related tasks... I can take a pass at updating the wiki <https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy> with this info, unless someone wants to suggest another option, or feels strongly about keeping the process the way it is. Thoughts, -Brian
