Releases/Firefox 5.0b5/BuildNotes: Difference between revisions

m
remove incorrect mentions of beta 4
m (remove incorrect mentions of beta 4)
 
(12 intermediate revisions by 2 users not shown)
Line 4: Line 4:
= Bugs hit =
= Bugs hit =
The following are the list of bugs that we expect to hit or that we did not expect to hit. For the next release some of this will be already fixed.
The following are the list of bugs that we expect to hit or that we did not expect to hit. For the next release some of this will be already fixed.
* {{bug|662803}} - Major update automation should support multiple "from" verions
 
* We forgot that beta4 was not shipped and update verify failed
 
These two required the manual work for major updates:
* {{bug|662803}} - Major update automation should support multiple "from" versions
* {{bug|662298}} - major update automation should be able to be run independently, or as part of the "to" release
* {{bug|662298}} - major update automation should be able to be run independently, or as part of the "to" release
Also check the "[[Release:Release_Automation_on_Mercurial/Known_Issues|known issues]]" page.
Also check the "[[Release:Release_Automation_on_Mercurial/Known_Issues|known issues]]" page.
== For postmortem ==
The whole release was rushed up (go to build later on EDT) and expectations of releasing on next afternoon was not explicit. If it was known I could have started things earlier.


=Build Engineers=
=Build Engineers=
Line 68: Line 76:
[cltbld@production-master03 builder_master]$ echo 6 > reserved_slaves_pm03  
[cltbld@production-master03 builder_master]$ echo 6 > reserved_slaves_pm03  
</pre>
</pre>
* Hit "ship it" button on "Firefox 5 Beta Build 4"</i> (https://l10n-stage-sj.mozilla.org/shipping/milestones)
* Hit "ship it" button on "Firefox 5 Beta Build 5"</i> (https://l10n-stage-sj.mozilla.org/shipping/milestones)
* Landed configs, merged configs & custom to production.
* Landed configs, merged configs & custom to production.
* Tagged buildbot-configs, buildbotcustom, and tools with FIREFOX_5_0b4_RELEASE and FIREFOX_5_0b4_BUILD1
* Tagged buildbot-configs, buildbotcustom, and tools with FIREFOX_5_0b5_RELEASE and FIREFOX_5_0b5_BUILD1
* Update pm03 checkouts & reconfigured
* Update pm03 checkouts & reconfigured
* Ran release_sanity dry run with:  
* Ran release_sanity dry run with:  
Line 123: Line 131:


=== L10n Verify ===
=== L10n Verify ===
TODO check
A few legitimate looking string changes.


=== Updates (5.0b[1-4] -> 5.0b5) ===
=== Updates (5.0b[1-4] -> 5.0b5) ===
Line 175: Line 183:
</pre>
</pre>
==== Update Verify ====
==== Update Verify ====
TODO
To force all of the verify builders, used the following script (warning: not OS X compatible):
<pre>
for p in linux linux64 macosx64 win32; do
  for i in `seq 1 10`; do
    curl "http://production-master1.build.sjc1.mozilla.com:8010/builders/release-mozilla-2.0-${p}_major_update_verify_${i}%2F10/force" >/dev/null
  done
done
</pre>
 
Differences in all platforms:
<pre>
diff -r source/firefox/defaults/pref/channel-prefs.js target/firefox/defaults/pref/channel-prefs.js
1,2c1,2
< //@line 2 "/builds/slave/rel-2.0-lnx-bld/build/browser/app/profile/channel-prefs.js"
< pref("app.update.channel", "release");
---
> //@line 2 "/builds/slave/rel-beta-lnx-bld/build/browser/app/profile/channel-prefs.js"
> pref("app.update.channel", "beta");
WARN: non-binary files found in diff
</pre>
 
Reviewing this GREEN logs are so verbose. How could this be improved?


=== Channel switching snippets ===
=== Channel switching snippets ===
Line 185: Line 214:
cd /opt/aus2/snippets/staging
cd /opt/aus2/snippets/staging
mkdir -p Firefox-5.0b5-build1-channel-switching/Firefox/
mkdir -p Firefox-5.0b5-build1-channel-switching/Firefox/
</pre>
<i>
rsync -a Firefox-5.0b5-build1-4.0.1-build1/Firefox/4.0.1 Firefox-5.0b5-build1-channel-switching/Firefox/
rsync -a Firefox-5.0b5-build1-4.0.1-build1/Firefox/4.0.1 Firefox-5.0b5-build1-channel-switching/Firefox/
cd Firefox-5.0b5-build1-channel-switching/Firefox/
cd Firefox-5.0b5-build1-channel-switching/Firefox/
Line 193: Line 220:
   mv -v $d/* $d/30000000000000
   mv -v $d/* $d/30000000000000
done
done
</i>
</pre>


=== Permissions check and A/V Scan ===
=== Permissions check and A/V Scan ===
Line 211: Line 238:


=== Final verify ===
=== Final verify ===
Triggered "release-mozilla-beta-$PLATFORM_final_verification" without any problems.
Using internal mirrors was so fast!!


=== Push snippets ===
=== Push snippets ===
"Firefox-5.0b5-build1" and "Firefox-5.0b5-build1-channel-switching" both only have a "5.0" version in them, so we only need one backupsnip between them. "Firefox-5.0b5-build1-4.0.1-build1" has 4.0 versions, and needs its own. As cltbld@aus2-staging, did the following for backups:
<pre>
cd /opt/aus2/snippets/staging
~/bin/backupsnip Firefox-5.0b5-build1
~/bin/backupsnip Firefox-5.0b5-build1-4.0.1-build1
</pre>
And for the pushes:
<pre>
~/bin/pushsnip Firefox-5.0b5-build1
~/bin/pushsnip Firefox-5.0b5-build1-channel-switching
~/bin/pushsnip Firefox-5.0b5-build1-4.0.1-build1
</pre>
Confirmed users
3,990

edits