SRU the current 3.36.2 stable update

[Sebastien Bacher]

* Impact
That's the current GNOME stable update which we believe falls under the 'New upstream microreleases' SRU exception
https://gitlab.gnome.org/GNOME/gnome-chess/-/blob/gnome-3-36/NEWS

* Test case

Play a chess game and ensure moves are correctly enforced and winning or losing is correct detected.

* Regression potential

Check for weird choices from the computer player since there are some fixes in the logic used there, especially errors detection.

[Brian Murray (brian-murray)]

From what I can tell gnome-chess is not part of the GNOME stable updates as it is not part of "the set of apps in core" nor does it ever appear in the discourse post regarding the GNOME MRU - https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/23. That being said the list in the post isn't very well sorted. Did I miss it anywhere?

[Sebastien Bacher (seb128)]

It's unclear to me how the GNOME MRU set is defined, gnome-chess has been a GNOME game shipping on the same schedule and following releases with the same versioning than GNOME and respecting their freezes since we ship Ubuntu. If it's not part of the MRU it's still a stable update and a valid SRU, is there a way to move forward with it as it is now or do we $changes?

[Brian Murray (brian-murray)]

If it is not part of the GNOME MRU set (which it isn't based off my interpretation of the set) then one way forward would be to provide information regarding how gnome-chess meets the criteria of a regular new upstream microrelease[1].

"For upstreams who have

  * a reliable and credible test suite for assuring the quality of every commit or release,
  * the tests are covering both functionality and API/ABI stability,
  * the tests run during package build to cover all architectures,
  * the package has an autopkgtest to run the tests in an Ubuntu environment against the actual binary packages"

[1] https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases

[Sebastien Bacher (seb128)]

> If it is not part of the GNOME MRU set (which it isn't based off my interpretation of the set)

I disagree it's not part of the set, it's follow GNOME schedule and freezes and the rational of the exception was to trust that component that follow GNOME freezes and schedules could be trusted, the games have always been in that position and that didn't change