Using the "patch" tag for bugs

Jordan Mantha mantha at
Wed Nov 28 08:26:42 GMT 2007

On Nov 26, 2007 12:50 PM, Jordan Mantha <mantha at> wrote:
> On Nov 26, 2007 8:04 AM, Emmet Hikory <persia at> wrote:
> > Fellow Developers,
> >     Malone currently tracks a flag for bug attachments that indicate
> > whether the bug is a patch or not, and we've a few URLs here and there
> > that point to bug searches that use this flag to select patches from
> > users that might be suitable for inclusion in the archive.  Recently,
> > I've had a couple new Contributors looking for ways to help mention to
> > me that some of the bugs returned by these searches don't contain any
> > patches, and my own investigations indicate that this mechanism seems
> > to have about a 50% hit rate.
> >
> I'm all for having a nice clean way of seeing which bugs have patches.
> I wonder though if the Launchpad system should be fixed rather than
> having two systems (LP flag and tag). It's kind of annoying to have
> two places/systems for the same thing.

To this end I had a talk with Christian (kiko) about maybe some things
that can be improved. I've come up with the following list of bugs
that may help. Please feel free to add to the discussion:
1. repeated bug in search for bugs with patches -
2. Can't mark a patch as obsolete -
3. show patch icon or notification on the comments page -
4. Rows in bug listings should indicate if a patch exists -
5. reject non-code patch attachements -
6. ability to convert a comment into a patch attachment -

I also think it's useful to have a tag to indicate a "triaged" patch,
that is one that is really a patch and ready for a dev to look at.


More information about the ubuntu-devel mailing list