Feature request: tracking of patches that are -stable candidates

Jeremy Kerr jk at ozlabs.org
Mon Sep 29 18:53:44 EST 2008

Hi Ted & Paul,

> I wonder if there's a simpler way to get the effect you want.  I
> suspect that the "stable candidate" state is really the interesting
> one.

Do you mean a state like Accepted/Rejected/etc?

The problem here is that you lose the actual state once you move it 
into "Stable Candidate". Was it accepted upstream, or rejected for some 
reason that doesn't preclude it from being added to stable?

It may be valid to have a patch that has 'Changes Requested', but we 
want to mark it (now, so we don't forget) for eventual inclusion in a 
stable series.

> Would it suffice to have a persistent, exported bundle for the 
> stable candidate patches, so that the "stable candidate" state is
> just the condition of being in the "stable-candidate" bundle?

One thing I was thinking about is tags - kind of like the current 
states, but a patch can have more than one tag. Tags would differ from 
bundles in that:

 * tags are global to all users (bundles being per-user)
 * the tags on a patch would appear on the patch page

We could use a similar interface to bundles - public pages to list the 
patches that have a particular tag, downloadable as an mbox.

How does that sound?


More information about the Patchwork mailing list