© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi Jeremy,
> There used to be a standing release exception from the Tech Board (TB) for GNOME microreleases but this explicit exception was dropped when the TB simplified the SRU policy in September 2015.
I was not aware of this. Thank you for pointing it out.
The current SRU policy is quite clear that a TB member must approve a micro release update where "such upstream automatic testing is not available". Based on your description I think this update falls under this TB approval requirement.
The thread at https:/
It seems to me that:
1. TB approved GNOME MRE having considered the QA requirements[1][2].
2. TB developed more general MRE requirements to save each MRE having to be individually approved by the tech board, and so dropped the previously documented MREs.
3. It wasn't noticed at the time that the GNOME MRE didn't meet the new generalised MRE requirements, so the GNOME MRE can't be approved by the SRU team on its own as the policy is written because it no longer meets the requirements.
However, I think it's clear that we should consider the GNOME MRE "grandfathered" and already accepted by the TB in their original acceptance of the MRE.
I've documented this at https:/
[1] https:/
[2] https:/