Exactly. I don't think we need to reopen this up to a bunch more changes, we can make more releases later. If I thought we would be opening a can of worms for this originally, I probably wouldn't have been in favor of it. My understanding was that 2.0.10 became 2.1.0 and more changes would follow on 2.x since we moved out 3.0.
-----Original Message----- From: Dan Fabulich [mailto:[EMAIL PROTECTED] Sent: Thursday, August 28, 2008 9:00 PM To: Maven Developers List Subject: RE: Maven 2.1.0 GA Plan +0.5 We should release that code that we did all that RC testing on, right away, and I don't care what we call it; I thought that was what John was proposing in his earlier [PROPOSAL]. -Dan Brian E. Fox wrote: > We've come this far, why not make 2.1.0 right now as we were doing > 2.0.10? I don't see any benefit to waiting longer. Just do it and then > we can start adding more things to 2.1.1 or 2.2 > > -----Original Message----- > From: John Casey [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2008 6:29 PM > To: Maven Developers List > Subject: Maven 2.1.0 GA Plan > > Hi everyone, > > So, it seems that we're all in agreement about the rough outline for > 2.1.x and beyond. I've renamed the current RC branch to be 2.1.0-M1-RC > to make this the first milestone toward some as-yet-undetermined feature > > list for 2.1.0. > > So, let's talk about that feature list. From earlier comments, I've > gathered that the following may be good targets to include for 2.1.0: > > - Dan's reactor changes > - Parallel downloads > - PGP stuff > - MNG-624 and related issues/feature enhancements (parent versioning, > right?) > > What I don't know is what state of maturity each of these is in, and on > what timeline they can be stabilized. Do the relevant developers have > enough time to finish implementing, testing, and documenting each > feature, so we could get a 2.1.0 GA out in, say 6 weeks or so? Maybe a > better approach would be to try for a new milestone release that > contains the final result of each new feature (with latent parts of the > rest, as we work on them), such that the 2.1.0 GA will contain all the > new features in their complete forms, with any regressions identified > fixed and incorporated? > > I haven't found the pertinent Confluence pages describing the above > features yet...maybe they don't exist or maybe I haven't looked hard > enough yet, but we'll need to collect the list somewhere that we can > make it public going forward, and then publish that release plan URL on > the Maven site. > > Are there other things that we can fit into this sort of timeframe? Is > this too much? It's my strong preference that we try to cap this release > > cycle at two months, so I guess this means taking the list of "nearly > there" features and determining whether we'll have the time to stabilize > > them for inclusion, given our current availability. > > Of course, once we settle the 2.1.0 release plan, we can start talking > about what we're going to do for 2.2, 2.3, etc. As long as we keep > things rolling, there's no reason anyone needs to feel overly rushed > about getting a particular feature in a particular release...it should > NOT be your only chance. :-) > > What does anyone else think? > > -john > > -- > John Casey > Developer, PMC Member - Apache Maven (http://maven.apache.org) > Blog: http://www.ejlife.net/blogs/buildchimp/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
