Every time a RC is made it is flagged off due to some bug or the other at the last moment.
I was wondering if before a RC is cut we take a pre-vote making sure that everyone has got sufficient time to test the branch for the features they are looking for ? Another suggestion is that since 4.3 is now close, why put our energies in 4.2.1 and instead focus on 4.3. -abhi On 30/12/13 2:26 am, "David Nalley" <da...@gnsa.us> wrote: >-1 (binding) because of the snapshot issues pointed out by Nux, >(CLOUDSTACK-5393) > >--David > >On Tue, Dec 17, 2013 at 5:49 AM, Abhinandan Prateek ><abhinandan.prat...@citrix.com> wrote: >> The 4.2.1 is re-spun mainly because the commit that was used to >>generate the previous RC did not get pushed to repo. >> >> Following are the particulars to vote for this time around: >> >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref >>s/heads/4.2 >> commit: 1b2b58fe352a19aee1721bd79b9d023d36e80ec5 >> >> List of changes are available in Release Notes, a summary can be >>accessed here: >> >>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=C >>HANGES;hb=4.2 >> >> Source release revision 3911 (checksums and signatures are available at >>the same location): >> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/ >> >> PGP release keys (signed using RSA Key ID = 42443AA1): >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS >> >> Vote will be open for 72 hours (until 20 Dec 2013 End of day PST). >> >> For sanity in tallying the vote, can PMC members please be sure to >>indicate "(binding)" with their vote? >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >>
