> -----Original Message-----
> From: Simon Weller [mailto:swel...@ena.com]
> Sent: Friday, September 20, 2013 8:05 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> round)
> 
> Animesh,
> 
> 
> Are you aware of any proposed upgrade documentation as of yet? I'd
> really like to try a couple of upgrades to test the procedure.
> 
> 
> - Si
[Animesh>]Here is the upgrade steps from RN for ACS 4.1.0 release. It should be 
the same for 4.1.0 to 4.2.0 
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1

> 
> ----- Original Message -----
> 
> From: "Animesh Chaturvedi" <animesh.chaturv...@citrix.com>
> To: dev@cloudstack.apache.org
> Sent: Friday, September 20, 2013 12:03:41 AM
> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> round)
> 
> 
> 
> > -----Original Message-----
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Thursday, September 19, 2013 5:15 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > round)
> >
> >
> >
> > > -----Original Message-----
> > > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > Sent: Thursday, September 19, 2013 4:46 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > > round)
> > >
> > > I prefer a respin, as painful as that seems. VPC is a major feature,
> > > do we really want to release something that we know will break
> > > anyone who tries to upgrade? I could deal with #1 if we are able to
> > > include the hotfix script in the packaging, such that the release
> > > notes can provide dead simple instructions for upgrade (no 'go
> > > download this script'). I'm just not clear on what we can change and
> > > what we can't
> > post-vote.
> >
> > [Animesh>] I don't think the release artifacts can be changed so the
> > script will have to be downloaded. David/Chip/Wido any thoughts on
> that?
> > We can have the script available before the release announcement if we
> > continue with current VOTE.
> >
> > >
> [Animesh>] Only Marcus, Indra and Simon have responded I am prepared to
> respin tomorrow after VPC testing is complete with fixes from Alena. I
> would like to stick to 72 hour VOTE including weekend since last time
> most of the VOTEs were received over weekend.
> 
> 
> > > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi
> > > <animesh.chaturv...@citrix.com> wrote:
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > >> Sent: Thursday, September 19, 2013 10:43 AM
> > > >> To: dev@cloudstack.apache.org
> > > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > >> (fifth
> > > >> round)
> > > >>
> > > >>
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > >> > Sent: Thursday, September 19, 2013 9:49 AM
> > > >> > To: dev@cloudstack.apache.org
> > > >> > 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.
> > > >>
> > > >> [Animesh>] I am also stumped why this was not caught earlier.
> > > >> Kishan has a fix that is being tested.
> > > > [Animesh>] So while the fix is being tested we have two options
> > > >
> > > > 1. Release 4.2, release note this issue, provide a separate script
> > > > that would have to be run if someone was using VPC in 4.1 and
> > > > upgraded to 4.2, fix this issue in 4.2.1
> > > >
> > > > 2. Since we have not released 4.2 yet, respin another RC and
> > > > another round of VOTE. That would be a record 6th RC Vote and 2
> > > > recalls after successful votes :(
> > > >
> > > > Thoughts?
> > > >
> > > >>
> > > >> > 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
> > > >> > > > >> =s
> > > >> > > > >> hor
> > > >> > > > >> tl
> > > >> > > > >> og;h
> > > >> > > > >> =
> > > >> > > > >> refs/heads/4.2
> > > >> > > > >> Commit: c1e24ff89f6d14d6ae74d12dbca108c35449030f
> > > >> > > > >>
> > > >> > > > >> List of changes:
> > > >> > > > >>
> > > >> > > > >> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git
> > > >> > > > >> ;a
> > > >> > > > >> =b
> > > >> > > > >> lob
> > > >> > > > >> _p
> > > >> > > > >> lain
> > > >> > > > >> ;
> > > >> > > > >> 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/KE
> > > >> > > > >> YS
> > > >> > > > >>
> > > >> > > > >> Testing instructions are here:
> > > >> > > > >>
> > > >> > > > >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/R
> > > >> > > > >> el
> > > >> > > > >> ea
> > > >> > > > >> se+
> > > >> > > > >> te
> > > >> > > > >> st+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)
> > > >> > > > >>
> > > >> > > > >>
> > > >> > >

Reply via email to