Releases/Firefox 38.0.6/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
38.0.6 is a Very Special release caused by {{bug|1171730}}. We'll be building all of the normal deliverables, but only shipping updates to win32 en-US users on Funnelcake builds (channel=release-cck-mozilla*). This release will also not be shipped on www.mozilla.org. Because of these things the normal checklist isn't going to be super helpful. Here's the rough order of operations, but it's by no means guaranteed to be complete or totally accurate.
38.0.6 is a Very Special release caused by {{bug|1171730}}. We'll be building all of the normal deliverables, but only shipping updates to en-US users on Funnelcake builds (channel=release-cck-mozilla*). This release will also not be shipped on www.mozilla.org. Because of these things we have to set-up extra Balrog rules by hand, so some parts of the checklist do not apply. If you're working on this release '''please read these notes carefully before taking any actions'''


* Submit to Ship It
= Checklist =
* After the win32_build completes:
* <s>(RelMan) [[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]] (build1 only)
** Manually run AV on en-US Windows build
* (RelMan) [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Submit_to_Ship_It | Submit to Ship It]]</s>
** Manually push to mirrors
* Set-up test updates (see below)
** Manually run updates builder + tweak rules
* [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]]
** Manually verify updates on release-cdntest-cck-mozilla*
* Publish updates (see below)
** Manually ship by tweaking rules in Balrog
* Post release (see below)


We will still let other platforms, locales, and partner repacks run to completion, and probably run the full AV scan + update verify, and maybe rsync them to the releases directory when completed. Having this full set of binaries in the end makes it much easier for us to generate partials against this version later if necessary.
== Set-up test updates ==
 
After the updates builder runs we need to do some stuff by hand to get the release-cdntest rules set-up to verify how we'll be shipping this. Here's what bhearsum thinks needs to happen:
== Manually run AV scan ==
* Revert product:Firefox, channel:release-cdntest rule back to 38.0.5 build4
Need to run this through extract_and_run_command.py. Look at an old av log to see an example.
* Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, locale:en-US, version:<38.0.5, priority:94, mapping:Firefox-38.0.6-build1-whatsnew
 
* Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, locale:en-US, priority:93, mapping:Firefox-38.0.6-build1
== Manually push to mirrors ==
Probably easiest just to look at an old push to mirrors log, copy/paste the rsync args, and run that for 38.0.6.
 
== Manually run updates builder ==
Once the en-US win32 build completes we've got all the binaries needed to ship, but not all of the information in release blob. To get this in place the "updates" builder should be run through force build. Hopefully it will succeed, though it's possible it may crap out when bumping a config. Once completed we need to do some additional rule tweaks to enable proper testing. The goal is that 38.0.6 should only be available for win32 en-US users on a channel matching "release-cck-mozilla*". We also want to make sure that only users coming from 38.0 and earlier receive a What's New Page. Here's something that should probably work:
* Revert product:Firefox, channel:release-cdntest rule back to 38.0.5
* Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, build target:WINNT_x86-msvc, locale:en-US, version:<38.0.5, priority:94, mapping:Firefox-38.0.6-build1-whatsnew
* Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, build target:WINNT_x86-msvc, locale:en-US, priority:93, mapping:Firefox-38.0.6-build1


Priorities from above are quite high because we already have 91 and 92 taken by the regular release channel WNP configuration.
Priorities from above are quite high because we already have 91 and 92 taken by the regular release channel WNP configuration.
Line 27: Line 19:
<big>'''TEST THE CRAP OUT OF THIS. THE AUTHOR IS NOT GUARANTING THAT THIS WILL WORK!!!!!!!'''</big>
<big>'''TEST THE CRAP OUT OF THIS. THE AUTHOR IS NOT GUARANTING THAT THIS WILL WORK!!!!!!!'''</big>


== Manually verify updates ==
=== Manually verify updates ===
Should verify at least the following:
Should verify at least the following:
{| class="fullwidth-table wikitable sortable"
{| class="fullwidth-table wikitable sortable"
Line 70: Line 62:
|}
|}


== Manually ship by tweaking rules in Balrog ==
== Publish updates ==
Need to port over the release-cdntest-cck-mozilla* rules. Be very careful, especially about the order of creation (highest priority first, maybe...)
Need to port over the release-cdntest-cck-mozilla* rules. Be very careful, and make sure to verify afterwards with the table above.
 
== Post release ==
* Remove index files from /pub/mozilla.org/firefox/releases/38.0.6 (by hand)
 
Do NOT update FTP symlinks or "-latest" entries in Bouncer.

Revision as of 19:06, 5 June 2015

38.0.6 is a Very Special release caused by bug 1171730. We'll be building all of the normal deliverables, but only shipping updates to en-US users on Funnelcake builds (channel=release-cck-mozilla*). This release will also not be shipped on www.mozilla.org. Because of these things we have to set-up extra Balrog rules by hand, so some parts of the checklist do not apply. If you're working on this release please read these notes carefully before taking any actions

Checklist

Set-up test updates

After the updates builder runs we need to do some stuff by hand to get the release-cdntest rules set-up to verify how we'll be shipping this. Here's what bhearsum thinks needs to happen:

  • Revert product:Firefox, channel:release-cdntest rule back to 38.0.5 build4
  • Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, locale:en-US, version:<38.0.5, priority:94, mapping:Firefox-38.0.6-build1-whatsnew
  • Add new rule for product:Firefox, channel:release-cdntest-cck-mozilla*, locale:en-US, priority:93, mapping:Firefox-38.0.6-build1

Priorities from above are quite high because we already have 91 and 92 taken by the regular release channel WNP configuration.

TEST THE CRAP OUT OF THIS. THE AUTHOR IS NOT GUARANTING THAT THIS WILL WORK!!!!!!!

Manually verify updates

Should verify at least the following:

Type Locale Platform Version Expected Result
Funnelcake en-US Windows 38.0 Update to 38.0.6 with what's new page
38.0.5 Update to 38.0.6 WITHOUT what's new page
Vanilla en-US Windows 38.0 Update to 38.0.5 with what's new page
38.0.5 No update
zu 38.0 Update to 38.0.5 WITHOUT what's new page
38.0.5 No update
en-US Mac 38.0 Update to 38.0.5 with what's new page
38.0.5 No update

Publish updates

Need to port over the release-cdntest-cck-mozilla* rules. Be very careful, and make sure to verify afterwards with the table above.

Post release

  • Remove index files from /pub/mozilla.org/firefox/releases/38.0.6 (by hand)

Do NOT update FTP symlinks or "-latest" entries in Bouncer.

Retrieved from "https://wiki.allizom.org/index.php?title=Releases/Firefox_38.0.6/BuildNotes&oldid=1078632"