Re: Commit fest queue - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Commit fest queue
Date
Msg-id 14144.1207936486@sss.pgh.pa.us
Whole thread Raw
In response to Re: Commit fest queue  ("Brendan Jurd" <direvus@gmail.com>)
Responses Re: Commit fest queue  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
"Brendan Jurd" <direvus@gmail.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.

In any case, this still sounds like forcing our problem to fit the tool.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Commit fest queue
Next
From: Heikki Linnakangas
Date:
Subject: Re: Remove lossy-operator RECHECK flag?