Is it valid if I mark a bug "Fix Committed" if the package in question is hosted upstream (outside of Launchpad)?
example: bug report, committed fix.
-
2This doesn't really belong here as it is not specific to Ubuntu. You should probably ask this question on Launchpad Answers.– dv3500eaNov 5, 2010 at 15:19
-
8It's useful for people doing bug work in ubuntu though: meta.askubuntu.com/questions/243/…– Jorge CastroNov 5, 2010 at 15:21
-
2@dv3500ea Launchpad is part of the Ubuntu Universe - so this does cover the scope (As @JorgeCastro pointed out)– Marco CeppiNov 5, 2010 at 16:39
-
@WarriorIng64 I was considering marking it a dupe, but the other question seems too developer oriented. I think it's worth a separate question– JjedFeb 2, 2012 at 14:10
-
1@WarriorIng64 you must have made a mistake there, cuz ur link points to this post– tshepangFeb 2, 2012 at 17:57
|
Show 2 more comments
5 Answers
"Fix Committed" means developers have figured out a working solution to a problem, and have it merged into their development repositories.
The problem will be delivered in updates when the bug is marked "Fix Released" for your Ubuntu version.
You shouldn't need to do this by hand. If you set a bug watch Launchpad can monitor upstream bug reports and set the status automatically. For this to work the project upstream needs to have it's bug tracker registered in Launchpad. (You can always add more if it's missing)
When you do this Launchpad will then track the bug in Ubuntu and upstream. That makes it easier for developers to find bugs that have been fixed upstream and not yet fixed in Ubuntu.
In your specific case wajig didn't have it's bug tracker registered in Launchpad. I went ahead and did that. Unfortunately the project in Launchpad isn't set to use the external bug tracker. You can probably contact the person who registered it to change it so that it points to the actual upstream wajig tracker, which will make it easy to link bug reports in the future.
Since that STILL doesn't solve your original problem I left a comment in the bug report; which will hopefully point the right people to the problem.
answered Nov 5, 2010 at 15:26
-
actually I don't want upstream bug tracker (code.google.com) to be linked to the package's LP page. No one uses that bug tracker. People instead report bugs directly here or in Debian, and that's fine with me, especially since the package is hardly useful outside of Debian land.– tshepangNov 5, 2010 at 16:48
You can find a list of Launchpad bug status definitions the way they are used in the Ubuntu bug tracker at https://wiki.ubuntu.com/Bugs/Status. Normally, for Ubuntu package tasks, "Fix Committed" doesn't correspond to "the fix is upstream but not in Ubuntu yet"; for that you can usually just set a bug watch and let Launchpad deal with it, as Jorge suggested.
Note that some Ubuntu teams assign different roles to certain Launchpad functions, including bug status; this can initially cause some confusion. If you're consistently triaging bugs in a particular component, it's a good idea to familiarize yourself with the way the team responsible for that component does bug triage.
-
the page you link to actually says that my bug should be marked "Fix Committed". Is that so?– tshepangNov 5, 2010 at 16:44
-
No. If you mean the "Upstream bug task: the fix is in CVS/SVN/bzr or committed to some place" bit, that applies to the upstream task (the uppermost line whose "Affects" field reads "wajig"), not the Ubuntu task (the one whose "Affects" field reads "wajig (Ubuntu)). If you set a bug watch, Launchpad will update the upstream task accordingly.– mgunesNov 5, 2010 at 16:55
No, Fix Committed is when the fix for said bug has been fixed in the code repository that the project uses.
Launchpad defines the status Fix Commited as "Fix Committed: a developer has committed his/her fix to the project's codebase." This means that the bug has been fixed by a developer, but it was not yet released, so you won't see that it has been fixed, until it gets into the state Fix Released.
