I thought the votes carrying over was meant to allow for expedited release of a new RC if only minimal changes were made against the previous one, like README changes or simple configs?
Are you saying you will carry over +1s when there were changes made to the RC that caused Mustella failures, which were subsequently fixed, after which even more changes were made? That seems wrong... Can you explain what type of changes between RCs you think warrant the nixing of previous votes and require new votes from scratch? For now, to help stop a new RC from immediately becoming a release if there were enough +1 votes for the previous, broken, RC: -1 (binding) EdB On Thu, Feb 27, 2014 at 12:06 PM, Justin Mclean <jus...@classsoftware.com>wrote: > Hi, > > Yes we will need a RC3, but people's +1 votes will carry over and all > feedback is good as it may reduce the need for an RC4. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
