Closed Bug 580010 Opened 10 years ago Closed 9 years ago

Tracking bug for build and release of Firefox 4.0beta2

Categories

(Release Engineering :: General, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(4 files, 5 obsolete files)

Waiting for "go to build".
Attachment #458564 - Flags: review?(nrthomas)
Attached patch automation bumps for 4.0b2 (obsolete) — Splinter Review
2 issues remain:

1) Should we use a separate l10nRevisionFile file? (l10n-changesets_firefox-central)

2) release_config1.py may be changed, if we decide to use pm02.
Attachment #458567 - Flags: review?(nrthomas)
Assignee: nobody → rail
Depends on: 568298
If we're using a separate l10n-changesets name, I'd go with its final name right away. Not sure I like our branch-based naming scheme, l10n-changesets_fx40x or just _fx4 might be easier to remember? Otherwise just _mozilla-2.0, I guess.

Nothing essential though, we can just hg mv them in another bug.

Further, the dashboard shipping page is https://l10n-stage-sj.mozilla.org/shipping/confirm-ship?ms=fx4.0b2, l10n-changesets need to be landed still. Permissions to ship granted to rail@ooo just now.
Comment on attachment 458564 [details] [diff] [review]
version bumps for mozilla-central to 4.0b3pre/2.0b3pre

Need to update config/milestone.txt too.
Attachment #458564 - Flags: review?(nrthomas) → review-
Attachment #458564 - Attachment is obsolete: true
Attachment #458587 - Flags: review?(nrthomas)
Comment on attachment 458567 [details] [diff] [review]
automation bumps for 4.0b2

>diff --git a/mozilla2/release-firefox-mozilla-central.py b/mozilla2/release-firefox-mozilla-central.py
> l10nRevisionFile   = 'l10n-changesets'

Lets use 'l10n-changesets_mozilla-2.0'. Please add that file to the diff.

> oldBuildNumber     = 1

This needs to change to 2 or we'll generate incorrect partials.

>+l10nPlatforms      = enUSPlatforms

>+releaseNotesUrl    = 'http://www.mozilla.com/firefox/4.0b2/releasenotes'

Lets change this to 'http://www.mozilla.com/%locale%/firefox/4.0b2/releasenotes/' like we meant to for b1.
Attachment #458567 - Flags: review?(nrthomas) → review-
Attachment #458587 - Flags: review?(nrthomas) → review+
Attached patch automation bumps for 4.0b2 (obsolete) — Splinter Review
* hg mv mozilla2/release-firefox-mozilla-{central,2.0}.py
* renamed update verify config file names (s/193/20/, see next patch for tools repo)
* updated mozilla2-staging directory

Note: this patch should be applied via "hg import --no-commit" not by patch(1)
Attachment #458567 - Attachment is obsolete: true
Attachment #458595 - Flags: review?(nrthomas)
Attachment #458596 - Flags: review?(nrthomas)
We also need to rename patcher-configs/moz193-branch-patcher2.cfg in CVS accordingly:

mv moz193-branch-patcher2.cfg moz20-branch-patcher2.cfg
cvs cvs remove moz193-branch-patcher2.cfg
cvs add moz20-branch-patcher2.cfg
cvs commit
Comment on attachment 458595 [details] [diff] [review]
automation bumps for 4.0b2

>diff --git a/mozilla2-staging/release-firefox-mozilla-central.py b/mozilla2-staging/release-firefox-mozilla-2.0.py
> binaryName          = 'MozillaDeveloperPreview'
> oldBinaryName       = 'MozillaDeveloperPreview'
> patcherToolsTag     = 'UPDATE_PACKAGING_R11'
>+binaryName          = 'Firefox'
>+oldBinaryName       = binaryName

Need to remove the old values for *binaryName on landing.
Attachment #458595 - Flags: review?(nrthomas) → review+
Attachment #458596 - Flags: review?(nrthomas) → review+
(In reply to comment #9)
> We also need to rename patcher-configs/moz193-branch-patcher2.cfg in CVS

Done.
Depends on: 576339
Attached patch automation bumps for 4.0b2 (obsolete) — Splinter Review
* Updated l10n-changesets_mozilla-2.0 file
* sourceRepoRevision = '3cc0b56a051'
Attachment #458595 - Attachment is obsolete: true
Attachment #458741 - Flags: review?(bhearsum)
Comment on attachment 458741 [details] [diff] [review]
automation bumps for 4.0b2

A couple things here:
* Update the l10nRevisionFile for staging, too
* Copy the mozilla-central config, don't rename it. We'll use it again at some point.

(Also need to pick up coop's changes, as you pointed out on IRC)
Attachment #458741 - Flags: review?(bhearsum) → review-
Attached patch automation bumps for 4.0b2 (obsolete) — Splinter Review
Attachment #458741 - Attachment is obsolete: true
Attachment #458752 - Flags: review?(bhearsum)
Comment on attachment 458752 [details] [diff] [review]
automation bumps for 4.0b2

You've got two "l10nRevisionFile" lines in the production version. This looks fine otherwise, though.
Attachment #458752 - Flags: review?(bhearsum) → review-
Take 4 (or 5?) :)
Attachment #458752 - Attachment is obsolete: true
Attachment #458758 - Flags: review?(bhearsum)
Comment on attachment 458758 [details] [diff] [review]
automation bumps for 4.0b2

looks good!
Attachment #458758 - Flags: review?(bhearsum) → review+
Comment on attachment 458596 [details] [diff] [review]
Rename update verify configs (tools)

changeset:   695:87f3fc03a038
Attachment #458596 - Flags: checked-in+
Comment on attachment 458758 [details] [diff] [review]
automation bumps for 4.0b2

changeset:   2717:45bb51c8d5e4
Attachment #458758 - Flags: checked-in+
Comment on attachment 458587 [details] [diff] [review]
version bumps for mozilla-central to 4.0b3pre/2.0b3pre

http://hg.mozilla.org/mozilla-central/rev/472acbffdcaa
Attachment #458587 - Flags: checked-in+
Comment on attachment 458758 [details] [diff] [review]
automation bumps for 4.0b2

Need to add this small change on top of this attachment
 http://hg.mozilla.org/build/buildbot-configs/rev/6ebd0a910469
for all the code churn.
Attachment #458933 - Flags: review?(bhearsum)
Attachment #458933 - Flags: review?(bhearsum) → review+
Comment on attachment 458933 [details] [diff] [review]
linux64 and macosx64 Tuxedo entries

http://hg.mozilla.org/build/tools/rev/55a2feeed926
Attachment #458933 - Flags: checked-in+
Shipped.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Opps. Wrong bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Shipped.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.