2
edits
ReleaseEngineering/How To/Generate partial updates: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/Generate partial updates (view source)
Revision as of 09:04, 12 July 2012
, 12 July 2012→Intro
(→Intro) |
|||
| Line 2: | Line 2: | ||
{{Release Engineering How To|Generate_partial_updates}} | {{Release Engineering How To|Generate_partial_updates}} | ||
<h1> Intro </h1> | |||
This document is about generating partial updates from older releases, eg N-2 to N, on request from Release Management. We generate N-1 to N updates in the release automation, but more than that is a manual process until {{bug|575317}} makes some progress. | <p>This document is about generating partial updates from older releases, eg N-2 to N, on request from Release Management. We generate N-1 to N updates in the release automation, but more than that is a manual process until <span class="fck_mw_template">{{bug|575317}}</span> makes some progress. | ||
</p><p>Assumptions: | |||
Assumptions: | </p> | ||
<ul><li> the automated updates builder has already run, and you're re-using the slave for the copy of the utilities and scripts you need | |||
</li><li> the request is for the release channel | |||
</li><li> all locales are being generated, possibly only some of the platforms | |||
</li></ul> | |||
For the purposes of this doc we'll say the update will be between $OLDV and $NEWV build$BUILD. The bug is $ | <p>For the purposes of this doc we'll say the update will be between $OLDV and $NEWV build$BUILD. The bug is $XXX<a href="http://www.freepornpump.com">XXX</a> | ||
</p> | |||
= Create config files = | = Create config files = | ||