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 - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
