UpdateGeneration: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 32: Line 32:


Steps for security release update generation:
Steps for security release update generation:
# Partial MARs and AUS configuration is generated using the patcher2 tool: http://mxr.mozilla.org/mozilla/source/tools/patcher/
* partial MARs and AUS configuration data are generated using the patcher2 tool: http://mxr.mozilla.org/mozilla/source/tools/patcher/
# The release engineer puts the appropriate URLs, version numbers, and build IDs into the patcher configuration file
* a release engineer puts the appropriate URLs, version numbers, and build IDs into the patcher configuration file: http://mxr.mozilla.org/mozilla/source/tools/patcher-configs/
# patcher downloads the complete MARs, creates partial diffs (using mbsdiff), and generates partial MAR files as well as AUS configuration files ("snippet" files).  
* patcher downloads the complete MARs, creates partial diffs (using mbsdiff), and generates partial MAR files as well as AUS configuration files ("snippet" files).  
# Patcher generates both production ("release") and testing ("releasetest") snippets, release snippets point to bouncer while releasetest snippets point to stage.
* patcher generates both production ("release") and testing ("releasetest") snippets, release snippets point to bouncer while releasetest snippets point to stage.
# The partial MAR files are copied to the candidates directory, and the releasetest snippets are loaded into AUS.
* partial MAR files are copied to the candidates directory, and the releasetest snippets are loaded into AUS.


=== Updates between major branches (aka major update) ===
=== Updates between major branches (aka major update) ===
canmove, Confirmed users
2,850

edits

Navigation menu