On 4 Sep 07, at 8:32 AM 4 Sep 07, Brett Porter wrote:
Hi,
Jason took care of 2.1-alpha-1, and Brian has kicked off a proposal
deadline, so that just leaves 2.1.x from the list I made earlier.
So I'll start spending some time tomorrow trying to pick the top
~100 highest priority / most addressable / related issues from
2.1.x to keep, then propose to cut the rest for now. I'll also go
through unscheduled. I know Deng already volunteered too - if she's
still available and if anyone else is around it will be pretty
short work.
Any objections?
How are you going to decide priority before all the proposals are in?
And I would pick features to implement not a 100 arbitrary issues.
The workflow should be:
- get all the proposals
- select the proposals containing the features we want to implement
- roadmap it across 2.1.x
- then chop jira apart
Handling bug fixes would be fine but anything related to features we
can do until all the proposals are in, and then people have to commit
to the proposals so that we know they will actually make it into the
release as we expect.
Thanks,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
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]
