Comment 311 for bug 1218322

@Sebastien:

I tried to refrain from commenting on this aspect, but it indeed made me think a lot. On one hand, I totally agree with you (myself also being a developer/contributor to open source). On the other hand, I share the frustration of many users, and I'm also quite disappointed on how such a complex and crucial bug could be slipped into a release and I share their opinion that the progress is way slower than it should be.

Is there a way you could please point me to documentation/guidelines how such bugs could slip into the distro, how such bugreports and prioritized/handled, what kind of QA process lets a distro ship with such a bug, whether the QA process will be revised to make sure such critical bug can't go into the distro in the future? I'd like to be sure that it's safe for me to stay with Ubuntu, but if there'll be one more release with such a critical bug, I'll just have to look for a different distribution. I'm not trying to offend anyone or criticize anything, but I'd like to know if what Ubuntu is able to offer to me is the best match for what I'm looking for, and right now I'm in serious doubt. In short: are there any *conclusions* drawn from this bug that'll help future Ubuntu releases become better?

I can't help to mention that the application I use the most frequently is gnome-terminal, where Ubuntu ships a quite old version, for exactly one reason: updating to a newer one requires shell work (touching /etc/profile or similar) to keep the convenience feature that new tabs open in the working directory of the current tab. Something that shouldn't take more than 10 minutes to solve, and even users can do it for themselves, still the distro couldn't yet solve it. I wonder: if such a trivial and easily workarounded issue is a blocker for a version update of gnome-terminal, how come that totally breaking the keyboard wasn't a blocker for the update of those components???