Reference¶
SRU series
The article series covers all aspects of Stable Release Updates (SRUs).
Understand the SRU process:
Stable Release Updates (SRU) - What SRUs are and how an update travels through the SRU pipeline
Principles - The principles behind the strict rules implying What is acceptable to SRU
About the SRU role - Who does what in the process, and the internal team docs
Perform an SRU:
Perform a standard SRU - How to fix a straightforward bug, step by step, and the common issues to avoid
Status pages - Track your SRU’s progress from sponsorship to release
SRU verification - Test the update in -proposed and report the results
Report a regression - Timely reports help to minimize impact
References in regard to the SRU process:
Prepare a special type of SRU - Special types such as staged uploads, NEW queue entries or package removals
Troubleshooting - How to Handle an autopkgtest failure or halted phased updates
SRU bug template - Used to Document how an SRU bug fulfills the criteria in a structured way
Package-specific notes - Standing exceptions for individual packages
This reference section contains technical information about the SRU workflow.
Tools and resources¶
Use the bug template while you document a package update and watch the progress of your SRU.
Standard processes and special cases¶
Learn more about the criteria to accept a package update, about your responsibilities when you submit an SRU and about all special cases.
Testing and SRU verification¶
Contact¶
On each working day, at least one SRU team member is available on public channels.