So, I've started tracking the features I proposed for 2.1.0 GA here:
http://docs.codehaus.org/display/MAVEN/Maven+2.1.0+Release+Plan
I don't know if this is the final list; IMO we'll need to agree on that
once we have design documentation for everything. I'm going to contact
Don Brown today and ask whether he can do a little write-up for parallel
resolution soonish, and I need to track down the build dynamism write-up
I put on Confluence (not to mention the relevant JIRAs for these
implementation changes). Ralph, once you have some design docs for the
automatic parent versioning, we'll add that in as well.
Please have a look, and give feedback! Thanks.
-john
John Casey wrote:
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]
