On Thu, Feb 18, 2010 at 03:52:49PM -0500, Scott Kitterman wrote: > > Regarding the team unification, is there an expectation that the two-vote > > approach will continue? I don't have a strong preference between the > > ubuntu-release and motu-release approaches, but I think it would be strange > > to be applying different procedures for different archive sections - or to > > different members of the team! - so we should probably pick one...
> I think it should go. IMO one of the main reasons to unify the teams is to > simply the process for people trying to work through getting needed > approvals. > If we have two separate rule sets, we may as well keep it two teams (I'm not > proposing we do this). I think the attached diff for FreezeExceptionProcess reflects the emerging consensus. Are there any objections if I apply this to the wiki and send out an updated freeze process mail to u-d-a? Are there any team delegations we want to have in place before sending out the announcement? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
--- tmpdCsjqP.moin.orig 2010-02-25 07:47:35.037545082 -0800 +++ tmpdCsjqP.moin 2010-02-25 07:58:00.317544338 -0800 @@ -139,7 +139,7 @@ == General Instructions == -Requests for freeze exceptions for `main` should be filed as bugs in launchpad against the relevant package (or just "Ubuntu" if the package is not available yet). Once the bug is filed and the necessary information is available, subscribe [[https://launchpad.net/~ubuntu-release|ubuntu-release]] (main, restricted) or [[https://launchpad.net/~motu-release|motu-release]] (universe, multiverse). All freeze exceptions must include the following information, in order to provide them with enough information to weigh the risk of regressions against the benefit of the changes: +Requests for freeze exceptions should be filed as bugs in launchpad against the relevant package (or just "Ubuntu" if the package is not available yet). Once the bug is filed and the necessary information is available, subscribe [[https://launchpad.net/~ubuntu-release|ubuntu-release]]. All freeze exceptions must include the following information, in order to provide them with enough information to weigh the risk of regressions against the benefit of the changes: * A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution * A rationale for the exception, explaining the benefit of the change @@ -157,25 +157,6 @@ * installs and upgrades, * does not break packages which depend on it, or that corresponding updates have been prepared. -== UserInterfaceFreeze Exceptions == - -The exception request bug report needs to have a justification why the user interface needs to be changed at that point, and give a rationale why the benefits of it are worth breaking existing documentation and translations. - -Every change of the user interface (either a string or the layout) requires you to notify the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc|documentation]] and [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators|translation]] teams. Please include a link to these posts in the mailing list archives of [[https://lists.ubuntu.com/archives/ubuntu-doc/|ubuntu-...@]] and [[https://lists.ubuntu.com/archives/ubuntu-translators/|ubuntu-translat...@]]. - -After that, subscribe the release team, as usual. - -== Milestone freeze Exceptions (like BetaFreeze) == - -During milestone/final release freeze periods, extreme caution is exercised when considering exceptions, as a regression could cause a deadline to be missed, or a build to receive less testing than desired. A request for an exception must demonstrate strong rationale and minimal risk for the update to be considered. - -Exception requests must include the following additional details: - - * It must fix a bug milestoned for that particular milestone. - * A complete `debdiff` of the proposed upload must be provided (preferably as bug attachment). - -== Exceptions for Universe/Multiverse == - === FeatureFreeze for new upstream versions === If you want to introduce a new upstream version with new features and/or ABI/API changes, please @@ -196,45 +177,63 @@ * for instance a copy and paste of the install messages from console when installing * mention what testing you've done to see that it works * a screenshot showing the main features could also be nice - * subscribe (not assign) it to the '`motu-release`' team. - * In some cases a standing freeze exception for multiple uploads is the most efficient way to manage the freeze process. Standing freeze exceptions should be requested in bugs using the normal process, although not all elements of a standard FFe request will apply. Once a standing FFe is approved (2 motu-release acks), it must be documented on the [[StandingFeatureFreeze|Standing Feature Freeze Exception]] page. + * subscribe (do not assign to) the '`ubuntu-release`' team. + * In some cases a standing freeze exception for multiple uploads is the most efficient way to manage the freeze process. Standing freeze exceptions should be requested in bugs using the normal process, although not all elements of a standard FFe request will apply. Once a standing FFe is approved, it must be documented on the [[StandingFeatureFreeze|Standing Feature Freeze Exception]] page. Please note that we expect requesters to have an updated package already prepared and tested! You will need this anyway to provide proper build logs. -Once the Feature Freeze Exception has been ACK'd by at least 2 members of the [[https://launchpad.net/~motu-release|MOTU Release Team]], the status will be changed to 'Confirmed`. You can then either upload the package (in case you're in [[http://launchpad.net/~motu|motu]] or [[http://launchpad.net/~ubuntu-core-dev|ubuntu-core-dev]]), or follow the [[SponsorshipProcess]]. +Once the Feature Freeze Exception has been ACK'd by a member of the [[https://launchpad.net/~ubuntu-release|Release Team]], the status will be changed to 'Confirmed`. You can then either upload the package (in case you're in [[http://launchpad.net/~motu|motu]] or [[http://launchpad.net/~ubuntu-core-dev|ubuntu-core-dev]]), or follow the [[SponsorshipProcess]]. References: - * [[https://bugs.launchpad.net/~motu-release/+subscribedbugs|Open requests]] + * [[https://bugs.launchpad.net/~ubuntu-release/+subscribedbugs|Open requests]] * [[https://lists.ubuntu.com/archives/ubuntu-motu/2006-February/000545.html|Original announcement]] - * UniverseFreeze -=== FeatureFreeze for bug fix only updates (process agreed by motu-release) === +=== FeatureFreeze for bugfix-only updates === Up through RC, if a MOTU believes upload of a new upstream release that just has bug fixes in it is warranted, they may upload it using this process: * [[https://launchpad.net/ubuntu/+filebug|File a bug]] in LP with the upstream change log entries in it (and rationale if it's not clear from that) * Mark it fix released when the upload is done to document that it was bug fix only - * If you have doubts about if something qualifies, check with a member of motu-release (or subscribe motu-release to the bug) and if one person from motu-release agrees it's a bug fix update, you're good for upload. + * If you have doubts about if something qualifies, check with a member of ubuntu-release (or subscribe ubuntu-release to the bug) and if one person from ubuntu-release agrees it's a bug fix update, you're good for upload. === FeatureFreeze for new packages === -The `motu-release` team will consider exceptions, where additions of packages are worthwhile (up until BetaFreeze). Please note: the `motu-release` team will not review the package for you. You should have followed [[UbuntuDevelopment/NewPackages]] before asking for an exception. +The `ubuntu-release` team will consider exceptions, where additions of packages are worthwhile (up until BetaFreeze). Please note: the `ubuntu-release` team will not review the package for you. You should have followed [[UbuntuDevelopment/NewPackages]] before asking for an exception. Process: * Follow [[UbuntuDevelopment/NewPackages]]. * File a bug, attach the source package to it (or link to it). - * subscribe (not assign) the bug to `motu-release`. + * subscribe (don't assign to) `ubuntu-release`. * State '''why''' the addition of the package should get considered. Decision: [[MOTU/Council/Meetings/2007-02-23]]. +== UserInterfaceFreeze Exceptions == + +The exception request bug report needs to have a justification why the user interface needs to be changed at that point, and give a rationale why the benefits of it are worth breaking existing documentation and translations. + +Every change of the user interface (either a string or the layout) requires you to notify the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc|documentation]] and [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators|translation]] teams. Please include a link to these posts in the mailing list archives of [[https://lists.ubuntu.com/archives/ubuntu-doc/|ubuntu-...@]] and [[https://lists.ubuntu.com/archives/ubuntu-translators/|ubuntu-translat...@]]. + +After that, subscribe the release team, as usual. + +== Milestone freeze Exceptions (like BetaFreeze) == + +During milestone/final release freeze periods, extreme caution is exercised when considering exceptions, as a regression could cause a deadline to be missed, or a build to receive less testing than desired. A request for an exception must demonstrate strong rationale and minimal risk for the update to be considered. + +Exception requests must include the following additional details: + + * It must fix a bug milestoned for that particular milestone. + * A complete `debdiff` of the proposed upload must be provided (preferably as bug attachment). + +== Exceptions for Universe/Multiverse == + === Milestone Freeze === During the last week of development before the release, all uploads need to get approved by the release team. Usually they ask a MOTU team for approval of Universe and Multiverse packages. Process: - * Either file a bug with the debdiff and assign it to `motu-release` and get approval for it. - * Or ask a member of the `motu-release` [[http://launchpad.net/~motu-release|team]] on IRC of approval for the debdiff. + * Either file a bug with the debdiff and assign it to `ubuntu-release` and get approval for it. + * Or ask a member of the `ubuntu-release` [[http://launchpad.net/~motu-release|team]] on IRC of approval for the debdiff. Decision: [[MOTU/Council/Meetings/2007-02-23]].
-- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
