[Tracker-discuss] tracker updates

[Stefan Seefeld]

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.

Regards,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...