You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/09/04 17:32:25 UTC
Cleaning up 2.1.x JIRA
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?
Thanks,
Brett
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
Re: Cleaning up 2.1.x JIRA
Posted by Brett Porter <br...@apache.org>.
Ok, I started at the bottom and worked up to MNG-1928. I'm starting
to get to the point where there is less cruft. I was particularly
conservative about things that might be good to have or related to
other stuff, and left comments where I could for people to write
proposals - I'm sure half of what I left in so far could also be
chopped though.
I'll carry on again tomorrow...
Cheers,
Brett
On 05/09/2007, at 9:34 AM, Brett Porter wrote:
>
> On 05/09/2007, at 5:29 AM, Jason van Zyl wrote:
>
>>
>> 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.
>
> New features account for about 10-15%, and improvements about 25%
> (I'm just guessing these from a pie chart). In unscheduled, it's a
> very small % of new features and about 25% improvements.
>
> So I think we can identify what are truly new features and apply
> the following:
> - if it is small or related to other things, it stays
> - if it is a "big thing" without a proposal, we can suggest they
> write one
>
> But mostly focus on cleaning up other than that..
>
>> 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.
>>
>
> Yep, no disagreement there.
>
> - Brett
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Cleaning up 2.1.x JIRA
Posted by Brett Porter <br...@apache.org>.
On 05/09/2007, at 5:29 AM, Jason van Zyl wrote:
>
> 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.
New features account for about 10-15%, and improvements about 25%
(I'm just guessing these from a pie chart). In unscheduled, it's a
very small % of new features and about 25% improvements.
So I think we can identify what are truly new features and apply the
following:
- if it is small or related to other things, it stays
- if it is a "big thing" without a proposal, we can suggest they
write one
But mostly focus on cleaning up other than that..
> 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.
>
Yep, no disagreement there.
- Brett
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Cleaning up 2.1.x JIRA
Posted by Jason van Zyl <ja...@maven.org>.
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 - brett@apache.org
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org