Re: Commit fest queue

On Apr 11, 2008, at 12:54 PM, Tom Lane wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)com> writes:
>> In Trac, if I just want to loosely associate several tickets together
>> I'd use *keywords*, e.g., put "index am" in the keywords list for
>> several tickets, and then they'll show up prominently when I search
>> for those terms.
>
> Assuming you know what to search for, of course ...
>
>> If I want something more structured I'd use a *milestone*. I'd
>> create
>> an "Index AM" milestone and attach all the relevant tickets to it.
>> Then I can easily pull up a report of all open tickets on the
>> Index AM
>> milestone (or all closed tickets, or all tickets regardless of
>> status,
>> or all tickets assigned to me, or all tickets not assigned to anyone
>> yet, or ...)
>
> Yeah, you can do all that in bugzilla too (Red Hat uses tracking bugs
> to such an extent that I think they outnumber the plain bugs :-().
> It still pretty much sucks for what I want, which is to easily see an
> overview of what's in the commit-fest queue organized in some helpful
> fashion.

Mozilla's bugzilla uses milestones to track what release something is
scheduled for... I'm thinking the same mechanism could be used for
commitfests (and releases).
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828