I think one of the issues is that practically all the community testing is based on new installs. Since we didn't appear to have a published upgrade procedure available for 4.x to 4.2, it made it very hard to test in a reliable way. I did try a couple of upgrades from 4.02 and 4.1 in my lab, and was unable to bring up the virtual routers (non VPC). But I assumed maybe I missed something in the upgrade procedure, so I didn't consider it valid.
We do need to have a think about how we can encourage the community to try upgrades and publish the results. But in order to do so, we need well documented upgrade steps to remove any ambiguity. - Si ----- Original Message ----- From: "Marcus Sorensen" <shadow...@gmail.com> To: dev@cloudstack.apache.org Sent: Thursday, September 19, 2013 11:49:26 AM Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round) We do need to ensure that we have the db upgrade fix that was mentioned on the other thread, otherwise people going from 4.1 to 4.2 will have their VPCs break. Looks like we are waiting on a script. It sounds like the plan will be to provide instructions in the release notes. Really wish we would have caught that, its not just that we find bugs at RC, but the severity of ones we miss is astounding sometimes. On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" < animesh.chaturv...@citrix.com> wrote: > > > > -----Original Message----- > > From: Wido den Hollander [mailto:w...@widodh.nl] > > Sent: Wednesday, September 18, 2013 4:55 PM > > To: dev@cloudstack.apache.org > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth > > round) > > > > > > > > On 09/19/2013 01:28 AM, Animesh Chaturvedi wrote: > > > > > > The vote has *passed* with the following results (binding PMC votes > > indicated with a "*" next to their name: > > > > > > +1 : Alex*, Chip*, Sebastien*, Prasanna*, Hugo*, Marcus*, Wido*, > > > +Sebastien, Rajesh Batala, Sheng, Vijay, Abhi, Likitha, Ian, Gavin, > > > +Daan, Amogh, Simon Weller, > > > > > > I'm going to proceed with moving the release into the distribution > > repo now and work on release notes and other documentation tasks. > > > > > Who is going to build the RPM and Deb packages? > > > > I think I should build the .deb packages since I'm the one in > > debian/changelog who set the version to 4.2 > > > > Give me a sign and I'll put the packages online in the DEB repo. > > > > Wido > [Animesh>] Chip/David do we need to wait for the docs to be closed out > first? > > > > > > > > Thanks > > > Animesh > > > > > > > > > > > > On Fri, Sep 13, 2013 at 4:12 PM, Animesh Chaturvedi < > > animesh.chaturv...@citrix.com> wrote: > > > > > >> > > >> I've created a 4.2.0 release, with the following artifacts up for a > > vote: > > >> > > >> Git Branch and Commit SH: > > >> > > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h > > >> = > > >> refs/heads/4.2 > > >> Commit: c1e24ff89f6d14d6ae74d12dbca108c35449030f > > >> > > >> List of changes: > > >> > > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain > > >> ; > > >> f=CHANGES;hb=4.2 > > >> > > >> Source release (checksums and signatures are available at the same > > >> location): > > >> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/ > > >> > > >> PGP release keys (signed using 94BE0D7C): > > >> https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > >> > > >> Testing instructions are here: > > >> > > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+p > > >> r > > >> ocedure > > >> > > >> Vote will be open for 72 hours (Wednesday 9/18 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) > > >> > > >> >
