On Mon, Jun 16, 2008 at 3:46 PM, Marc Fargas <[EMAIL PROTECTED]> wrote: > El lun, 16-06-2008 a las 11:28 +0800, Russell Keith-Magee escribió: >> A bug/feature keyword won't >> give you anywhere as much attention, but it will help us filter out >> features from the list of work we need to focus on. > > I took the other way around, I'm adding the keyword "post10" for tickets > that can wait until 1.0 so a negative filter would give you "pre10" and > "yet-to-be-marked-tickets". Hope that makes life a bit easier (but I've > only marked about 5 tickets).
Marking everything that _wont_ be in v1.0 will be a lot more work than making sure we can find everything that _will_ be v1.0. We would like to aspire to having Zero Bugs (or, at least, Zarro Boogs) for v1.0. Therefore, all we need to be able to do is eliminate any feature proposal (whether accepted, DDR or someday/maybe) from a 'todo list' search. There are already 26 tickets marked 'feature'; IMHO, the best tagging approach would be to continue this trend. Tag any feature specifically included for v1.0 with a v1 keyword, any feature without the v1 keyword will be ignored, and assume everything else is a bug, and needs to be addressed for v1.0. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
