SeaMonkey:Release Process:2.35: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Create Page)
 
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{RTOC}}
{{RTOC}}
<small>[[Releases/SeaMonkey2.33|&laquo; SeaMonkey 2.33]]</small>
<small>[[Releases/SeaMonkey2.35|&laquo; SeaMonkey 2.35]]</small>


== Build Harness ==
== Build Harness ==
Line 6: Line 6:


== Bugs ==
== Bugs ==
Tracking bug filed as {{bug|?}}.
Tracking bug filed as {{bug|1177025}}.


== Build Engineer ==
== Build Engineer ==
Line 12: Line 12:


== Signed-off Revisions ==
== Signed-off Revisions ==
{{hg|??|releases/comm-release|;releases/comm-release
(build1)
:}}
{{hg|e6dcddf50595|releases/comm-release|;releases/comm-release
{{hg|??|releases/mozilla-release|;releases/mozilla-release
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
:}}<br><small>??_RELBRANCH</small>
{{hg|cf6b17cea869|releases/mozilla-esr38|;releases/mozilla-esr38
{{hg|DOMI_2_0_15|dom-inspector|;dom-inspector
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
{{hg|SEA2_26_RELBRANCH|dom-inspector|;dom-inspector
:}}<br><small></small>
:}}<br><small></small>
{{hg|SEA2_26_RELBRANCH|chatzilla|;chatzilla
:}}<br><small></small>
(build2)
{{hg|4c0855a2be32|releases/comm-release|;releases/comm-release
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
{{hg|cf6b17cea869|releases/mozilla-esr38|;releases/mozilla-esr38
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
{{hg|SEAMONKEY_2_35_BUILD1|dom-inspector|;dom-inspector
:}}<br><small>SEA_COMM3820_20150821_RELBRANCH</small>
{{hg|SEA2_26_RELBRANCH|chatzilla|;chatzilla
:}}<br><small></small>
(build3)
{{hg|b939f5c5904d|releases/comm-release|;releases/comm-release
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
{{hg|cf6b17cea869|releases/mozilla-esr38|;releases/mozilla-esr38
:}}<br><small>SEAMONKEY_2_35_RELEASE_BRANCH</small>
{{hg|SEAMONKEY_2_35_BUILD1|dom-inspector|;dom-inspector
:}}<br><small>SEA_COMM3820_20150821_RELBRANCH</small>
{{hg|SEA2_26_RELBRANCH|chatzilla|;chatzilla
{{hg|SEA2_26_RELBRANCH|chatzilla|;chatzilla
:}}<br><small></small>
:}}<br><small></small>
Line 23: Line 44:
venkman is no longer included in the release.
venkman is no longer included in the release.


L10n revisions according to opt-ins as taken from the [https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=sea2.33.1 sign-off tool] (and pushed '''ship-it''').
L10n revisions according to opt-ins as taken from the [https://l10n-stage-sj.mozilla.org/shipping/l10n-changesets?ms=sea2.35 sign-off tool] (and pushed '''ship-it''').


== Notes ==
== Notes ==
Line 36: Line 57:
* Updated and reconfigured buildmaster
* Updated and reconfigured buildmaster
* Kicked off with the following command:
* Kicked off with the following command:
  bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.33build1" doit
  bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build1" doit
* Tagging failed due to not having the proper cset for Inspector.
** Callek fixed it by doing some cset magic
* All Builds failed due to not having the proper SOCORRO api token setup.
 
=== Build2 ===
bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build2" doit
* Tagging : Ok
* Builds : failed due to pushing the wrong patch to c-r.
 
=== Build3 ===
bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build3" doit
<!--
<!--
* Tagging finished fine.
* Tagging
* All Builds good.
* Builds  
* All repacks good.
-->
-->


Line 62: Line 93:
*_l10n_verify and updates started automatically, triggered by the fake-signing.
*_l10n_verify and updates started automatically, triggered by the fake-signing.
** L10n verification is mostly useless, since we have lots of expected changed strings.
** L10n verification is mostly useless, since we have lots of expected changed strings.
* Update good.
* Update failed due to patcher path issues, but with a bit of magic, Callek unhorked it and it went green.
* Update Verification was good.
* Update Verification broke due to path issues in verify.sh. Changed reference paths in verify.sh and the workdir that verify.sh and the command to call verify.sh finally unhorked the verifications (particularly macosx64).


=== Copy Language Packs ===
=== Copy Language Packs ===
Line 95: Line 126:
=== Push website updates Live ===
=== Push website updates Live ===


locally:
[Starting with SeaMonkey 2.35, we have migrated away from CVS, and so the old cvs method no longer works.  Here's the new way:]
cvs up -Pd


Then do the <code>cvs add</code> command described in our website bug (if not already done)
# Clone website (if not done)  
#* hg clone http://hg.mozilla.org/SeaMonkey/seamonkey-project-org website
# cd website
# Import patch
#* hg qimport <patch>
# Finish patch
#* hg qfinish <patch>
# Push patch to website repo
#* hg push ssh://hg.mozilla.org/SeaMonkey/seamonkey-project-org


Last:
[NO MORE CVS! YAY!]
patch -p0 < patch && cvs ci -m ....


=== Push Updates to the beta Channel ===
=== Push Updates to the beta Channel ===
Line 108: Line 145:


On aus |/opt/aus2/snippets/staging/|:
On aus |/opt/aus2/snippets/staging/|:
  ~/bin/backupsnip Sea*2.33-build1
  ~/bin/backupsnip Sea*2.35-build1
  ~/bin/pushsnip Sea*2.33-build1
  ~/bin/pushsnip Sea*2.35-build1


=== Send Announce ===
=== Send Announce ===
Send the announcement to newsgroups and about-mozilla.
Send the announcement to newsgroups and about-mozilla.

Latest revision as of 00:53, 8 September 2015

« SeaMonkey 2.35

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 1177025.

Build Engineer

  • ewong (mentor: Callek)

Signed-off Revisions

(build1)

releases/comm-release
 e6dcddf50595
SEAMONKEY_2_35_RELEASE_BRANCH
releases/mozilla-esr38
 cf6b17cea869
SEAMONKEY_2_35_RELEASE_BRANCH
dom-inspector
 SEA2_26_RELBRANCH
chatzilla
 SEA2_26_RELBRANCH

(build2)

releases/comm-release
 4c0855a2be32
SEAMONKEY_2_35_RELEASE_BRANCH
releases/mozilla-esr38
 cf6b17cea869
SEAMONKEY_2_35_RELEASE_BRANCH
dom-inspector
 SEAMONKEY_2_35_BUILD1
SEA_COMM3820_20150821_RELBRANCH
chatzilla
 SEA2_26_RELBRANCH

(build3)

releases/comm-release
 b939f5c5904d
SEAMONKEY_2_35_RELEASE_BRANCH
releases/mozilla-esr38
 cf6b17cea869
SEAMONKEY_2_35_RELEASE_BRANCH
dom-inspector
 SEAMONKEY_2_35_BUILD1
SEA_COMM3820_20150821_RELBRANCH
chatzilla
 SEA2_26_RELBRANCH

venkman is no longer included in the release.

L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it).

Notes

WE ARE HERE

Build

  • Made sure all build machines have clean release directories.
    • With clobberer
  • Updated buildbot-configs for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build1" doit
  • Tagging failed due to not having the proper cset for Inspector.
    • Callek fixed it by doing some cset magic
  • All Builds failed due to not having the proper SOCORRO api token setup.

Build2

bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build2" doit
  • Tagging : Ok
  • Builds : failed due to pushing the wrong patch to c-r.

Build3

bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.35build3" doit

Update Version for stage scripts

On stage-old.mozilla.org, modified ~/versions.sh for the current release run.


Signing

  • We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
  • Logged onto stage-old.mozilla.org and ran sh ~/fakesign.sh
  • signing good

Send info to metrics

No longer needed to send info to metrics.


Updates and Verification

  • _l10n_verify and updates started automatically, triggered by the fake-signing.
    • L10n verification is mostly useless, since we have lots of expected changed strings.
  • Update failed due to patcher path issues, but with a bit of magic, Callek unhorked it and it went green.
  • Update Verification broke due to path issues in verify.sh. Changed reference paths in verify.sh and the workdir that verify.sh and the command to call verify.sh finally unhorked the verifications (particularly macosx64).

Copy Language Packs

Used langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.

Zipcopy

Used zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.


Create Checksums

With make-checksums.sh as documented in 2.0.3 notes, created MD5SUMS and SHA1SUMS files containing all files we release - copying the README from last time and replacing the versions as needed, as well as doing the same for Linux x86_64.


Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.15b2 win32 (all locales) for them to scan, and be sure there are no false-positives.

  • Used |viruspush.sh| on stage for this.

E-mailed our TrendMicro contact to let him know of the new version available on their FTP server.

Push To Mirrors

Used mirrorpush.sh as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.


Final Verification

Used 'Force Build' to start the final_verification builder; all tested URLs are HTTP 200 and 302 - ready for going public!

Push website updates Live

[Starting with SeaMonkey 2.35, we have migrated away from CVS, and so the old cvs method no longer works. Here's the new way:]

  1. Clone website (if not done)
  2. cd website
  3. Import patch
    • hg qimport <patch>
  4. Finish patch
    • hg qfinish <patch>
  5. Push patch to website repo

[NO MORE CVS! YAY!]

Push Updates to the beta Channel

Once website updates are live

On aus |/opt/aus2/snippets/staging/|: 

~/bin/backupsnip Sea*2.35-build1
~/bin/pushsnip Sea*2.35-build1

Send Announce

Send the announcement to newsgroups and about-mozilla.

Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.35&oldid=1094100"