[Tracker-discuss] tracker updates
pfdubois at gmail.com
Sun Nov 26 01:09:22 CET 2006
Yeah, I get it, but what I meant was that by default there is no such
action; 'superceder' in the classic tracker sounds nice but it does bupkiss.
BTW can we make this list default to 'reply to list'?
On 11/25/06, Stefan Seefeld <seefeld at sympatico.ca> wrote:
> Paul Dubois wrote:
> > This reminds me of a question I have been meaning to ask. I don't think
> > 'superceder' actually does anything in 'classic'. I ended up changing it
> > to mean 'see also' in my tracker. Is superceder actually supposed to
> > have some action associated with it?
> I think the idea is to be able to have a long-term process that spans
> multiple bugs, so you can close one bug and indicate that some followup
> will be handled elsewhere.
> In particular, in my suggested schema a duplicate bug would be closed
> as 'duplicate' with the superseder field set to the bug this one is a
> duplicate of.
> So, I think while 'see also' merely means that two bugs are somehow
> related, 'superseder' has stronger semantics implying that the superdeded
> bug is actually closed.
> ...ich hab' noch einen Koffer in Berlin...
> Tracker-discuss mailing list
> Tracker-discuss at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tracker-discuss