GNOME Shell and Mutter had been covered by Ubuntu’s GNOME MicroReleaseException “MRE” policy that allows for new point releases to ship rather easily as stable updates to existing Ubuntu Linux releases.
But breaking the camel’s back is GNOME 46.1 shipping explicit sync support.
Due to landing a “significant new feature” into a point release, the GNOME Shell and Mutter are no longer covered by this exception.
But the intent is that the point releases are focused on just fixing bugs and not adding new features or other big changes.
Longtime Ubuntu developer Christopher James Halse Rogers announced today that GNOME Shell and Mutter are no longer covered by this exception: "It has been brought to the SRU team’s attention that mutter has landed a significant new feature in the 46.1 point release.
The GNOME MicroReleaseException policy historically exists on the basis that the GNOME release and testing process broadly matches SRU policy, so duplicating that process by performing a full SRU review on GNOME point releases would be unnecessary work.
The original article contains 251 words, the summary contains 170 words. Saved 32%. I’m a bot and I’m open source!
This is the best summary I could come up with:
GNOME Shell and Mutter had been covered by Ubuntu’s GNOME MicroReleaseException “MRE” policy that allows for new point releases to ship rather easily as stable updates to existing Ubuntu Linux releases.
But breaking the camel’s back is GNOME 46.1 shipping explicit sync support.
Due to landing a “significant new feature” into a point release, the GNOME Shell and Mutter are no longer covered by this exception.
But the intent is that the point releases are focused on just fixing bugs and not adding new features or other big changes.
Longtime Ubuntu developer Christopher James Halse Rogers announced today that GNOME Shell and Mutter are no longer covered by this exception: "It has been brought to the SRU team’s attention that mutter has landed a significant new feature in the 46.1 point release.
The GNOME MicroReleaseException policy historically exists on the basis that the GNOME release and testing process broadly matches SRU policy, so duplicating that process by performing a full SRU review on GNOME point releases would be unnecessary work.
The original article contains 251 words, the summary contains 170 words. Saved 32%. I’m a bot and I’m open source!