Ubuntu 12.04 LTS "Precise Pangolin" released [LWN.net]

Ubuntu 12.04 LTS "Precise Pangolin" released

Posted Apr 27, 2012 18:55 UTC (Fri) by alecs1 (guest, #46699)
In reply to: Ubuntu 12.04 LTS "Precise Pangolin" released by mathstuf
Parent article: Ubuntu 12.04 LTS "Precise Pangolin" released

Obviously, many things in life are a question of compromise. Yeah, he saved 5 minutes. Can someone claim that the decision the maintainer made was not a mistake? I think I stated my arguments on this particular bug completely enough to cover your examples.

I don't use Ubuntu (mainly because of poor upgradability, but while testing I did give up Unity precisely because of Klipper), but should I get treated like the reporter, I'll just leave, and not necessarily to Debian. And guess what, Ditto is a better replacement to Klipper and works OK on all Windows versions I tried. And Lyx will accept my bug report and donations from Windows too. Same will stand for Pidgin, Marble, Okular and QtCreator etc.

I'll stop, and also apologise Harald Sitter that I chose his bug to exemplify what I consider a costly mistake. I'd also report the bug and link it from Launchpad, but I have no idea if it reproduces.

(Log in to post comments)

Ubuntu 12.04 LTS "Precise Pangolin" released

Posted Apr 27, 2012 19:11 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

I hadn't looked at your case specifically. I was more responding to what seemed that the user should never have to forward bugs to upstream.

Looking at it, it was indeed handled poorly (overall). Instead of being closed as Invalid, it should probably have been kept open and some indication that there was an upstream bug to be tracked in it (I'm a Fedora maintainer and an RHBZ bug can be associated with other BZs). That way, when the upstream bug is fixed, it can be asked to be backported or whatever on the distro side. Of course, I don't know the Ubuntu bug life cycle, so maybe this was "valid" under that, but I'd say if that was the case, the lifecycle needs fixed.

Ubuntu 12.04 LTS "Precise Pangolin" released

Posted Apr 29, 2012 10:41 UTC (Sun) by jond (subscriber, #37669) [Link]

The op should report the bug. The lp person should have politely asked them to do so. Follow-ups to the upstream bug need to go to the original reporter, not the middleman.

Ubuntu 12.04 LTS "Precise Pangolin" released

Posted Apr 29, 2012 14:46 UTC (Sun) by mathstuf (subscriber, #69389) [Link]

Even so, the lp bug shouldn't be marked as closed (and certainly not Invalid!). At least on BZ, CLOSED bugs need an extra step to search for, so keeping it open with a reference to the upstream bug is always better than closing the bug if it isn't actually fixed in Ubuntu. The reporter can come back to lp (though I would say that the maintainer should probably at least go CC'd on the upstream bug) and notify the maintainer that a fix is available. At that point the maintainer can decide whether it's important enough to backport or just wait for the next version.