It's quite frustrating that people find time to write hundreds of mails about points of procedure, but can't take time to review a release tarball from a podling.
Activity on Bloodhound is picking up, and the project wants to release every couple weeks; yet the 0.2 vote thread sat in general@ for longer than that. It's worse for these mails to go unanswered than if the release had been vetoed. I hereby propose we extend the silent consensus rule to podling release votes. -- Brane On 26.11.2012 16:59, Joachim Dreimann wrote: > Hi, > > I would like to request the beginning of the vote for the third release of > Apache Bloodhound in the incubator following the successful vote by the > Bloodhound PPMC. > > The result of the vote is summarised here: > http://markmail.org/thread/owksv6lbcs6zq7th > > The artefacts for the release including the source distribution and KEYS > can be found here: > https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ > > The release itself is created from: > https://svn.apache.org/repos/asf/incubator/bloodhound/tags/0.3-incubating/ > (r1412891) > > Issues identified to be fixed for the next release are listed here: > https://issues.apache.org/bloodhound/ticket/273 > https://issues.apache.org/bloodhound/ticket/274 > > The vote will be open for at least 72 hours. > > [ ] +1 Release this package as Apache Bloodhound 0.3 > [ ] +0 Don't care > [ ] -1 Do not release this package (please explain) > > Cheers, > Joe > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
