Release:Release Automation on Mercurial:Updates through Shipping: Difference between revisions

Release:Release Automation on Mercurial:Updates through Shipping (view source)

932 bytes removed , 24 February 2015

Confirmed users

3,104

edits

@@ Line 17: / Line 17: @@
 Note that both the sourceRepo and the tools repo will be updated to the patcherToolsTag. If the update-packaging tools or patcher config script has been updated since the last release it is a good idea (and sometimes necessary) to create a new UPDATE_PACKAGING_R# tag before starting the release. [[ReleaseEngineering/PatcherTags]] documents the tag history, please keep it up to date.
-== Snippet Comparison Log Analysis ==
-Once updates is completed there will be a log from the snippet comparison step. This step compares the contents of the releasetest channel snippets to the contents of the live channel (beta or release) snippets. There's a few things to note about this log:
-* It will usually contain warnings about missing snippets for alphas and betas. These are expected and ignorable.
-* When there are warnings about other snippets missing, a 'Warnings' log will be created and the step will be orange. These must be investigated and explained/fixed before any live snippets are pushed.
-* If any snippets differ in contents between the test and live channels a 'Diffs' log will be created and the step will be orange. The Diffs log will list the files which differ; the full diffs can be viewed in the stdio log. Any differences must be investigated and explained/fixed before any live snippets are pushed.
 = Set-up whatsnew page =