Comment 359 for bug 160311
Revision history for this message
| Andrea Corbellini (andrea.corbellini) wrote | #359 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> If I understand this bug's description correctly, this problem exists in Unity-2D on
> Ubuntu 12.04 "Precise Pangolin". This is an LTS release - according to
> https:/
> the server until April 2017. This should mean fully and wholly supported, not
> partly supported.
That's true, but 'supported' means "security and severe bug fixes only". See https:/
> I also disagree with marking this bug's unity-2d task as Invalid while the upstream GNOME
> bug is still open
Also, you should note that the situation in the GNOME bug is a bit different. Firstly, there is no consensus on whether Metacity or the theme(s) should be fixed. Secondly, whilist Metacity has not been deprecated (AFAIK), it is no longer the development focus of GNOME. In fact, the last comment made by a developer was made on 2011-01-10.
> as this implies that even if GNOME were to develop and deploy a fix,
> Ubuntu would not adopt the fix.
I removed the metacity task just to make it clear that this bug is closed and to reduce the bug noise. This does not imply that if a fix is released by GNOME, then it won't be adopted by Ubuntu. We do not 'filter' upstream code. If Metacity makes a new release with the fix included, then it will just be packaged.
> And of course the fact that GNOME are considering fixing
> this issue should not in any way preclude Ubuntu from attempting to fix it.
Again, you are free to open a bug about it, although I doubt it will be fixed as there are no developers working on Metacity on Ubuntu. Anyhow, the point is: this particular one is too old and too long to be useful. Your opinions are welcome, but if you continue posting here, they will just be ignored.