Activity log for bug #1021326

Date Who What changed Old value New value Message
2012-07-05 14:28:34 Evan bug added bug
2012-07-05 14:37:04 Evan description The vast majority of developers viewing http://errors.ubuntu.com will be targeting Ubuntu. Showing versions from many different derivatives just creates noise - there may be a version bump in a Elementary that does not fix the issue, but effectively hides the last version of the package in the Ubuntu archive which experienced the bug from the front page view. So lets just show versions from official Ubuntu sources in the "First seen" and "Last seen" fields. Equally, selecting a specific Ubuntu release at the top of the page should show the "First seen" and "Last seen" fields for that release. We'll also provide a breakdown of versions a problem has been experienced on, which includes derivative versions, on the individual problem pages. Context: [15:06:59] <seb128> I'm still trying to figure what to do for 12.04.1 [15:07:12] <seb128> we have been trying to increase the bug fixing [15:07:36] <seb128> but the current errors.ubuntu.com lack of features,details make it hard to have a good picture [15:08:06] <seb128> like the "running version vs installed version" issues makes it hard to figure if the issue was really fixed or not [15:08:25] <seb128> and we don't have details of the repartition of the issues across versions [15:08:44] <seb128> so it's hard to see what has been really fixed, what didn't get fixed, was is due to users who didn't upgrade yet... The vast majority of developers viewing http://errors.ubuntu.com will be targeting Ubuntu. Showing versions from many different derivatives just creates noise - there may be a version bump in a Elementary that does not fix the issue, but effectively hides the last version of the package in the Ubuntu archive which experienced the bug from the front page view. So lets just show versions from official Ubuntu sources in the "First seen" and "Last seen" fields. Equally, selecting a specific Ubuntu release at the top of the page should show the "First seen" and "Last seen" fields for that release. We'll also provide a breakdown of versions a problem has been experienced on, which includes derivative versions, on the individual problem pages (bug 1021332). Context: [15:06:59] <seb128> I'm still trying to figure what to do for 12.04.1 [15:07:12] <seb128> we have been trying to increase the bug fixing [15:07:36] <seb128> but the current errors.ubuntu.com lack of features,details make it hard to have a good picture [15:08:06] <seb128> like the "running version vs installed version" issues makes it hard to figure if the issue was really fixed or not [15:08:25] <seb128> and we don't have details of the repartition of the issues across versions [15:08:44] <seb128> so it's hard to see what has been really fixed, what didn't get fixed, was is due to users who didn't upgrade yet...
2012-07-05 14:37:10 Evan bug task added daisy
2012-07-05 14:37:30 Evan daisy: importance Undecided High
2012-07-05 14:37:30 Evan daisy: status New Confirmed
2012-07-05 14:37:40 Evan errors: importance Undecided High
2012-07-05 14:37:40 Evan errors: status New Confirmed
2012-08-14 21:02:25 Evan errors: status Confirmed Invalid
2012-08-14 21:02:35 Evan daisy: status Confirmed Fix Committed
2012-11-09 18:51:29 Matthew Paul Thomas description The vast majority of developers viewing http://errors.ubuntu.com will be targeting Ubuntu. Showing versions from many different derivatives just creates noise - there may be a version bump in a Elementary that does not fix the issue, but effectively hides the last version of the package in the Ubuntu archive which experienced the bug from the front page view. So lets just show versions from official Ubuntu sources in the "First seen" and "Last seen" fields. Equally, selecting a specific Ubuntu release at the top of the page should show the "First seen" and "Last seen" fields for that release. We'll also provide a breakdown of versions a problem has been experienced on, which includes derivative versions, on the individual problem pages (bug 1021332). Context: [15:06:59] <seb128> I'm still trying to figure what to do for 12.04.1 [15:07:12] <seb128> we have been trying to increase the bug fixing [15:07:36] <seb128> but the current errors.ubuntu.com lack of features,details make it hard to have a good picture [15:08:06] <seb128> like the "running version vs installed version" issues makes it hard to figure if the issue was really fixed or not [15:08:25] <seb128> and we don't have details of the repartition of the issues across versions [15:08:44] <seb128> so it's hard to see what has been really fixed, what didn't get fixed, was is due to users who didn't upgrade yet... The vast majority of developers viewing http://errors.ubuntu.com will be targeting Ubuntu. Showing versions from many different derivatives just creates noise - there may be a version bump in a Elementary that does not fix the issue, but effectively hides the last version of the package in the Ubuntu archive which experienced the bug from the front page view. So lets just show versions from official Ubuntu sources in the "First seen" and "Last seen" fields. Equally, selecting a specific Ubuntu release at the top of the page should show the "First seen" and "Last seen" fields for that release. We'll also provide a breakdown of versions a problem has been experienced on, which includes derivative versions, on the individual problem pages (bug 1021332). Context: [15:06:59] <seb128> I'm still trying to figure what to do for 12.04.1 [15:07:12] <seb128> we have been trying to increase the bug fixing [15:07:36] <seb128> but the current errors.ubuntu.com lack of features,details make it hard to have a good picture [15:08:06] <seb128> like the "running version vs installed version" issues makes it hard to figure if the issue was really fixed or not [15:08:25] <seb128> and we don't have details of the repartition of the issues across versions [15:08:44] <seb128> so it's hard to see what has been really fixed, what didn't get fixed, was is due to users who didn't upgrade yet... It may save time to fix bug 1056061 at the same time as this bug.
2012-12-03 10:20:37 Evan daisy: status Fix Committed Fix Released