Hi,
The first big milestone of getting Maven 2.0.7 out the door has just
passed (kudos Jason, and all the patchers and testers!)
It seems we're chomping at the bit to get some 2.1 work kicking
along, and I just wanted to understand the plan of action... let me
know if others agree this is where we are at.
We have the 'prep list' to work through at: http://jira.codehaus.org/
secure/IssueNavigator.jspa?fixfor=13535&sorter/
field=priority&mode=hide&reset=true&pid=10332&sorter/order=ASC
From this, the blocker to starting proposals is only the taxonomy
which must be very close to being finished (in fact, some proposals
are already going in). The blocker to planning any releases is the
JIRA stuff (I will get it done, it just needs to be documented, I'm
just in a particularly coding frame of mind right now so I'm doing
that instead), then the blocker to coding anything is the IT stuff
and dev process. The patch stuff only blocks the release (though it
would be helpful to apply against 2.0.x too, so the sooner the better).
So, steps would be:
1) check taxonomy stuff is finished, kick it around so everyone is
happy with it and understands how it should be used.
2) gather up all the proposals people have going around and get them
into the wiki
3) finish sorting out jira issues (by this point, we should have a
list of all the things going into 2.1 and 2.1.x)
4) plan the 2.1 releases from a new feature perspective -
collectively pick what we can get done from the wiki. Get them into
JIRA too. The other proposals are still active, and will be
reconsidered for future releases.
5) map out the incremental releases (around 4 weeks apart for 2.1-
alpha-1, alpha-2, etc), and which jiras are incorporated
6) get the IT stuff and development expectations sorted out
7) start implementing things
8) releases!
All the while, other efforts like 2.0.x, plugins and site changes
continue as is.
Is this what others understand the current plan to be?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
