Yes, apologies. Last time I wasn't sure what caused it, now I know it's because bh-dev was in the to: field.
I'll highlight this in my write up of the release process that I'll publish soon. - Joe ________________________ @jdreimann - Twitter Sent from my phone On 26 Nov 2012, at 20:27, Branko Čibej <[email protected]> wrote: > Sigh ... got caught out again buy the silly reply-to. These incubator > vote threads shoulg go TO: general@incubator, not to bloodhound-dev and > only cc: general@incubator, or this will happen all the time > > -- Brane > > On 26.11.2012 21:25, Branko Čibej wrote: >> 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) >> +1 (binding) >> >> -- Brane > > > -- > Branko Čibej > Director of Subversion | WANdisco | www.wandisco.com >
