| From | Sent On | Attachments |
|---|---|---|
| Ewan Mellor | Aug 16, 2012 7:39 pm | |
| Brett Porter | Aug 16, 2012 8:25 pm | |
| Ewan Mellor | Aug 16, 2012 8:30 pm | |
| Brett Porter | Aug 16, 2012 9:26 pm |
| Subject: | RE: Release plan update | |
|---|---|---|
| From: | Ewan Mellor (Ewan...@eu.citrix.com) | |
| Date: | Aug 16, 2012 8:30:46 pm | |
| List: | org.apache.incubator.cloudstack-dev | |
-----Original Message----- From: Brett Porter [mailto:bre...@porterclan.net] On Behalf Of Brett Porter Sent: 16 August 2012 20:26 To: clou...@incubator.apache.org Subject: Re: Release plan update
On 17/08/2012, at 12:40 PM, Ewan Mellor <Ewan...@eu.citrix.com> wrote:
Stability and bugfix work: Now - Friday 31 August. First release candidate build: Friday 31 August.
This is just my $A0.02 as someone that cares a lot about release automation... take it for what it is worth, since I'm not doing the work :)
Given release candidates are not distributed, official releases, would you consider an earlier one that may have some known issues, but is ready enough to test that your release mechanism works?
Having something concrete that says "this is what our release will look like, once the following things are complete" that can start to be reviewed from an incubator release point of view could parallelise something that often takes a bit of time going back and forth.
I've got two weeks between First release candidate build and Final release
candidate. Are you saying that the incubator review needs even more time than
this?
Ewan.





