On 21 Jun 07, at 6:48 PM 21 Jun 07, Brett Porter wrote:
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.
I will coalesce these three pages to mesh:
http://docs.codehaus.org/display/MAVEN/Taxonomy
http://docs.codehaus.org/display/MAVEN/Maven+Taxonomy
http://docs.codehaus.org/display/MAVEN/Architectural+Goals+for+Maven+2.1
Where the first one is the simplest and closest. In one place I've
taken a taxonomy entry "POM" and create "POM :: Encoding" and put
that as a component in JIRA. So given the lack of hierarchies with
components in JIRA that's how I decided to represent the hierarchy.
I'm sure after a little burst it won't change a whole lot and will be
altered when additions are made and new categories made when new
features require it. Basically it will be adding the component to
JIRA and linking in the doco related to the taxonomy entry.
2) gather up all the proposals people have going around and get
them into the wiki
If people now want to start jamming stuff in then hook them off here:
http://docs.codehaus.org/display/MAVEN/Architectural+Goals+for+Maven+2.1
Even if a bit of a mess now and I'll reintegrate into the taxonomy.
Then at least folks interested in changes know where they are.
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)
It could still use a serious scrub but it's relatively ok now.
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.
As were working on things I think as many alphas can go out as we can
possibly squeeze out even if it was one a week. I think we start
scrutinizing the releases once the first beta is close.
5) map out the incremental releases (around 4 weeks apart for 2.1-
alpha-1, alpha-2, etc), and which jiras are incorporated
I think until the first beta arrives bash them out as fast as
possible. We can start his anytime provide people are aware that it's
alpha and though pretty stable they use it at their own risk and if
you use it for production builds you will have an exciting time.
6) get the IT stuff and development expectations sorted out
I think this needs to be moved further up and made a priority and can
be done far before any planning of formal beta releases. They are
quite a clusterfuck with all the coupling to production plugins and
requiring a network connection. Making these shine will be the key
being able to move quickly on new development.
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?
We also need to plan:
- the separation of the sites, not sure if this has been sorted or not
- reporting using swizzle which will help us immensely in making
decisions about what to focus on, the voting in JIRA is too crude
- release process
- new features/refactorings be done on branches so that trunk as
much as possible does not destabilize and people can collaborate
while sweeping changes are made
- the completion of work John T started to make generating the
information to vote on would make releasing quickly and accurately a
possibility
- the release plugin or something else needs to be made to take
care of secondary deployments, site deploy (this can't be done as
part of the release because a screw up site deployment should not
affect a binary release), announcements, and whatever else
We can stick those in JIRA and link it from here:
http://docs.codehaus.org/display/MAVEN/Home
There is no way to sequence this stuff in JIRA is there?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
