Launchpad bug statuses
Forest Bond
forest at alittletooquiet.net
Tue Oct 2 22:09:03 BST 2007
Hi,
On Tue, Oct 02, 2007 at 11:00:49PM +0200, Emilio Pozuelo Monfort wrote:
> Christian Robottom Reis wrote:
> > On Tue, Oct 02, 2007 at 04:50:20PM -0400, Forest Bond wrote:
> >> Hi,
> >>
> >> On Tue, Oct 02, 2007 at 09:14:34PM +0200, Sebastien Bacher wrote:
> >>> * "Fix Committed (Please Test My Fix)"
> >>>
> >>> The status is used by the some teams to mark bugs which have been fixed
> >>> upstream since it makes easier to review bugs that have a patch to
> >>> backport or should be closed when the next version is uploaded
> >> Isn't the correct way to handle this to add the upstream project to launchpad
> >> and set the bug so that it also affects upstream? Then you can be explicit
> >> about the bug's status upstream.
> >>
> >> This came up recently here:
> >>
> >> https://bugs.launchpad.net/ubuntu/+source/newt/+bug/54555
> >
> > Well, the issue is that Sebastian would like to be able to look at
> > Ubuntu bugs and see which ones have been fixed upstream and which ones
> > haven't. But I argue there is already a report that tells him that, in
> > the advanced page of the bug search.
>
> That is in case the bug report has an upstream task, but that isn't
> always the case.
>
> For example, I usually forward Liferea bugs upstream on IRC, and the
> upstream developer directly fixes it in SVN. What I do then is mark the
> Ubuntu bug as Fix Committed, with the intention to close it with the
> next bug-fix release.
The upstream project is created automatically when you mark a bug as affecting
it, isn't it? That what I thought I remembered.
-Forest
--
Forest Bond
http://www.alittletooquiet.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20071002/9f278db0/attachment.pgp
More information about the ubuntu-devel
mailing list