Re: [xwiki-devs] [PROPOSAL] Release process/dates for 4.1-rc-1

Hi Caleb, Sorry I had read this mail too quickly before. I see an issue with what you propose: you're removing 1 week of development. What we had decided in the roadmap was: * RC1 on 11th * Final on 18th I don't really understand what you're trying to achieve with the staging. Is it to replace the notion of RC? So far our staging was 1 week, between the 11th and 18th. Now it seems you wish to replace that one week by staging directly the final on 6th till 11th. Thus loosing 1 week of time. IMO we shouldn't have both staging it's useless and eats up precious dev time. So if we keep the dates decided (I don't see any reason to change them) you should start the staging on 11th. We have 2 choices: 1) Staging the final on 11th and promoting it on the 18th 2) Staging the RC on 11th and releasing, letting users have a go at it and then release final on 18th If we choose option 1) we need to be prepared to restage every time we find a problem. We would also need to amend our current overall process, announcements and all our POMs (since they currently say 4.1-rc-1 AFAIK). I have an important preference for 2) since doing 2 will mean the RC1 release will appear on our download page and be announced on all channels this leading to more testing. If we do 1) are you going to announce it as a release on the download page and such? If not, then it's definitely not as good as 2). So right now I'm 1+ for 2) and -0 (very close to -1) for 1). I'm also -1 to do 2 staging since I don't see the usefulness (please explain so that I understand). Maybe I misunderstood something?

Thanks -Vincent On May 31, 2012, at 6:54 PM, Caleb James DeLisle wrote: > In order to try meet a release date, I would like to use the process as documented here: > > http://dev.xwiki.org/xwiki/bin/view/Community/ReleasePlans#H4.1RC1 > > Synopsis: > > June 4th: > * send 2 day warning mail, ask if anyone needs to block the release. > * branch stable-4.1.x to allow 4.2 development to continue. > > June 6th: > * build staged release. > * send out call for testing. > * do release on jira with release post-dated to the 11th. > > June 11th: > * release from staging. > * publish release. > > > I know this is a tight schedule but realistically we need 2 days for warning/stabilization > and 2 (working) days for testing. > > WDYT? > > Caleb