Just to clarify: releases can't be vetoed, not even by binding PMC votes. As long as there are at least 3 binding +1 votes, it's up to the release manager, i.e. Massimo in this case, to decide whether to bury it or proceed.
I agree it's unfortunate that a fix for a problem in 5.3 did not make it into the first bugfix release but that's not a reason to hold up the release. That being said, Ulrich Stärk: +1 (binding) On 14.12.2011 23:17, David Rees wrote: > > On Wed, Dec 14, 2011 at 12:45 PM, Bob Harner <bobhar...@gmail.com> wrote: >> It does appear to be a regression from 5.3. It reportedly only appears >> when upgrading to 5.3. I don't have any further details myself other >> than what's in the bug report and the mailing list thread on the >> topic. > No, it's a regression in 5.3 not from 5.3 and not a regression in > 5.3.1. So in my (non-binding) opinion, it should not hold up a 5.3.1 > release. If it were introduced in 5.3.1 then I would agree with you. > > -Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org >
