+1 for M2 On Tue, Mar 18, 2008 at 8:52 PM, Mike Heath <[EMAIL PROTECTED]> wrote:
> +1 for an M2 release. > > Emmanuel Lecharny wrote: > > 이희승 (Trustin Lee) wrote: > >> Hi, > >> > >> We have fixed 26 issues since 2.0.0-M1. Although we have 13 more > >> issues to resolve in M2, I think we can slide to M3 considering the > >> number of resolved issue so far. > > I think that releasing milestones frequently is not a bad idea, but if > > it only contains bugs fixes, I'm not sure they should be named > > milestone. I would suggest something slightly different : > > > > - Milestones should mark a progression toward a complet functionnal > > version. So between Mx and M(x+1), you should see new functionalities > > and some bugfixes > > I think an M2 release would fall under this definition. We've fixed > bugs and added features but there's still work to be done. I agree. > > > > - when you think that all the new functions have been added, then you > > switch to a RCx scheme. > > RC stands for 'release candidate' so in my mind, an RC release means > that the RC release will become the final release unless a major bug is > found. I hate RC releases that are actually beta releases. > > > However, I think : > > - it's too late to adopt this new scheme now, as we already have a M2 > > running > > - and I should have propose that before in order to be discussed and > > possibly adopted :) > > > > That being said, yeah, sure, with 26 fixed issues, it deserve a new > > milestone ! > > Perhaps we should come up with a better defined road map in JIRA so that > our milestone release are actually reaching a predetermined milestone. > We should schedule out the remaining milestone(s) and any feature > request not scheduled for a specific milestone will get pushed to a > future release. This would give us a clear target for a beta release > and eventually a final 2.0 release. Sounds good. Maarten > > > WDYT? > > -Mike >
