Re: [boost] Patches in trac...
On Wed, Apr 8, 2009 at 6:24 PM, Marshall Clow <marshall@idio.com> wrote:
The conclusion that was reached at the end of the discussion was that we wanted to get rid of the "Patches" label for Trac tickets, and to move all the existing patches to either "Bugs" or "Feature Requests".
What do people think?
You might want to add a keyword "patch" to all tickets containing a patch. Just to make it searchable. /$
Henrik Sundberg wrote:
On Wed, Apr 8, 2009 at 6:24 PM, Marshall Clow <marshall@idio.com> wrote:
The conclusion that was reached at the end of the discussion was that we wanted to get rid of the "Patches" label for Trac tickets, and to move all the existing patches to either "Bugs" or "Feature Requests".
What do people think?
You might want to add a keyword "patch" to all tickets containing a patch. Just to make it searchable.
One can also add a custom field for this. The Django project has four extra checkboxes on their tickets to see this state. Perhaps overkill for Boost, but definitely food for thought. See http://code.djangoproject.com/ticket/13 f.ex. Cheers, /Marcus
on Wed Apr 08 2009, Marcus Lindblom <macke-AT-yar.nu> wrote:
One can also add a custom field for this.
The Django project has four extra checkboxes on their tickets to see this state. Perhaps overkill for Boost, but definitely food for thought.
See http://code.djangoproject.com/ticket/13 f.ex.
I don't think that's overkill at all; it would be very useful to be able to sort our tickets that way. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
David Abrahams wrote:
on Wed Apr 08 2009, Marcus Lindblom <macke-AT-yar.nu> wrote:
One can also add a custom field for this.
The Django project has four extra checkboxes on their tickets to see this state. Perhaps overkill for Boost, but definitely food for thought.
See http://code.djangoproject.com/ticket/13 f.ex.
I don't think that's overkill at all; it would be very useful to be able to sort our tickets that way.
Ok. It's a 1 min edit to conf/trac.ini, so it's easy to do. The hard part is probably to describe the workflow and steal^h^h^hadd one or two reports. :) Cheers, /Marcus
participants (3)
-
David Abrahams -
Henrik Sundberg -
Marcus Lindblom