| 2007-05-06 04:41:08 |
William Grant |
bug |
|
|
added bug |
| 2007-05-07 22:02:24 |
Diogo Matsubara |
malone: status |
Unconfirmed |
Needs Info |
|
| 2007-05-07 22:02:24 |
Diogo Matsubara |
malone: statusexplanation |
|
Hello William,
could you please add specific examples where that happened?
Cheers. |
|
| 2007-05-08 13:43:43 |
Björn Tillenius |
malone: status |
Needs Info |
Confirmed |
|
| 2007-05-08 13:43:43 |
Björn Tillenius |
malone: assignee |
|
bjornt |
|
| 2007-05-08 13:43:43 |
Björn Tillenius |
malone: statusexplanation |
Hello William,
could you please add specific examples where that happened?
Cheers. |
Manual tests show that this shouldn't happen (so it probably works in most cases), but the bug's activity log confirms that it did happen. I'm not sure what's wrong, though, I'll have to take a closer look at it. If you run into this issue again, feel free to add the bug number to this bug, it makes it easier to debug. |
|
| 2007-06-06 08:48:46 |
Björn Tillenius |
description |
With the release of Feisty, a new distorelease for Gutsy was added. This inadvertently reopened quite a number of bugs that were already fixed.
In some cases (mostly security bugs) a task is opened for each release that is affected, including the development release. Once there is a task for the development release, Launchpad disables the main Ubuntu task. During the bug's lifetime, it is marked as fixed in each release as appropriate. All is good. But when another distrorelease appears, the main Ubuntu task is silently turned back on and reopened. This is wrong, as Gutsy is derived from Feisty, so has all the fixes in it at release time. |
With the release of Feisty, a new distorelease for Gutsy was added. This inadvertently reopened some bugs that were already fixed.
In some cases (mostly security bugs) a task is opened for each release that is affected, including the development release. Once there is a task for the development release, Launchpad disables the main Ubuntu task. During the bug's lifetime, it is marked as fixed in each release as appropriate. All is good. But when another distrorelease appears, the main Ubuntu task is silently turned back on and reopened. This is wrong, as Gutsy is derived from Feisty, so has all the fixes in it at release time.
This happens when the current release gets Rejected, and then later marked Fix Released. In this case the underlying Ubuntu task will keep the status it had before, and not be marked Fix Released as it should. |
|
| 2007-06-06 08:48:46 |
Björn Tillenius |
title |
Addition of a new distrorelease can reopen many bugs |
Addition of a new distrorelease can reopen some bugs |
|
| 2008-07-28 18:28:38 |
Christian Reis |
malone: status |
Confirmed |
Incomplete |
|
| 2008-07-28 22:19:47 |
William Grant |
malone: status |
Incomplete |
New |
|
| 2008-09-08 14:13:29 |
Björn Tillenius |
malone: status |
New |
Triaged |
|
| 2008-09-08 14:13:29 |
Björn Tillenius |
malone: statusexplanation |
Plain Ubuntu meaning a Distribution task, not a DistroSeries task. Before the Gutsy DistroSeries was added to Launchpad, ubuntu/feisty/wireshark and ubuntu/wireshark were conjoined (as Feisty was the development focus), and ubuntu/feisty/wireshark was marked 'Fix Released'.
The normal behaviour when a new DistroSeries is made the development series is to split the bugtasks, and the conjoined slave (ubuntu/wireshark) is available again, with the attributes it last inherited from the conjoined master.
Apparently in this case the conjoined master hadn't been pushing updates to its slave, or they got reset when the new DistroSeries opened - the ubuntu/wireshark task became open as soon as Gutsy appeared. |
|
|
| 2009-09-08 06:52:53 |
Björn Tillenius |
malone: assignee |
Björn Tillenius (bjornt) |
|
|
| 2009-10-09 00:03:17 |
Curtis Hovey |
tags |
|
tech-debt |
|
| 2010-11-22 04:58:23 |
Curtis Hovey |
malone: importance |
Undecided |
Low |
|
| 2013-08-22 09:16:41 |
William Grant |
launchpad: status |
Triaged |
Fix Released |
|
