Stable Release Updates policy

William Grant william.grant at ubuntu.com.au
Tue Oct 31 04:26:27 GMT 2006


Hi,

ajmitch brought up the Stable Release Updates policy draft 
(http://wiki.ubuntu.com/MOTU/SRU) in #ubuntu-motu earlier today. A couple of 
hours of discussion ensued, resulting in the development of a process which 
all non-security updates to stable releases for universe and multiverse must 
go through. The proposed process was developed by imbrandon, LaserJock, 
ajmitch, lifeless and myself (Fujitsu), and is as follows:

 * The initial debdiff is uploaded to the bug by a MOTU (or ACKd by one, if
   uploaded by a non-MOTU).
 * The MOTU (or the MOTU that approved the debdiff) uploads the package
   to -proposed for wider testing.
 * The packages stays in -proposed until at least 5 people add "works for me"
   comments to the bug, and at least 5 days have passed since it was uploaded
   to -proposed.
 * Once those two conditions have been met, the motu-sru team is subscribed to
   the bug.
 * After the motu-sru team OKs the update, the MOTU uploads the package
   to -updates.
 * The motu-sru team and the author of the debdiff remain as bug contacts for
   the package for at least the following 2 weeks in order to get
   notifications of any regressions.

The purpose of this email is to attract further comments on this process from 
more people than just those involved in the IRC discussion earlier today. So, 
feel free to reply to the list with any criticism/praise/support/whatever, or 
add such comments to the bottom of the aforementioned page on the wiki, and 
we'll hopefully have a reasonable stable release update policy in the near 
future!

Thanks,

William Grant.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20061031/2dc63c29/attachment.pgp 


More information about the Ubuntu-motu mailing list