[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: DEP-3: Patch Tagging Guidelines



Le vendredi 19 juin 2009 à 10:55 +0200, Raphael Hertzog a écrit :
> > It’s already better, but for more readability, would it be possible to
> > have a registered list of bug tracking aliases? For example:
> >         Bug-Debian: #12345
> >         Bug-Ubuntu: #2356
> >         Bug-GNOME: #5671
> 
> It should be possible. I see one problem here though. Bug-Gnome is really
> "Bug" because it's the upstream bug. While we can have an URL mapping for
> each vendor, it's not possible for the non-qualified entry used for the
> upstream case.

I don’t think one of these entries should be qualified as “the”
canonical upstream bug.

When I forward a bug to epiphany, if I add a Bug: pointing to GNOME,
later it can be forwarded by them to Mozilla/Webkit because the patch
turns out to be a workaround for a bug in the engine. That would make
suddenly the Bug field turn into a Bug-GNOME, and a new Bug field would
be introduced, pointing to Mozilla/Webkit?

I think it’s bad design to rely on too much expectations based on a
particular case. The only thing that’s generic is that patches are
related to bugs that can lie in various trackers.

-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=


Reply to: