Closed Bug 663820 Opened 14 years ago Closed 14 years ago

Setup "mozilla-release" branch

Categories

(Release Engineering :: General, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: bhearsum)

References

Details

Attachments

(2 files, 1 obsolete file)

As part of rapid release cadence, we will no longer be doing a new repo per each feature release (the old approach was to create release/mozilla-1.9.1, release/mozilla-1.9.2, etc. Instead we will ship a series of features releases from the same new "mozilla-release" repos. The repo will live at hg.m.o/releases/mozilla-release. The l10n repos will live at releases/l10n/mozilla-release. Update channel in the mozconfigs should be 'aurora'.
(In reply to comment #0) > Update channel in the mozconfigs should be 'aurora'. Is this a typo? We won't be doing nightlies here, AFAIK, and the release mozconfigs should be set to "release".
can I hijack this bug and get comm-release setup at the same time? Or shall I file a new bug?
Blocks: 663894
Assignee: nobody → bhearsum
Depends on: 663947
Depends on: 663954
Depends on: 664112
Depends on: 664113
Attached patch add mozilla-release branch (obsolete) — Splinter Review
Lukas, this is very similar to the mozilla-beta patches, except I trimmed out unnecessary config variables (a few from l10n, a bunch of nightly update related stuff). I've been testing in staging on http://dev-master01.build.scl1.mozilla.com:8118/one_line_per_build and http://dev-master01.build.scl1.mozilla.com:8018/one_line_per_build Ignoring the graph server/log upload failures (which are now fixed), things are looking good.
Attachment #539188 - Flags: review?(lsblakk)
Comment on attachment 539188 [details] [diff] [review] add mozilla-release branch r+ with the change on mobile nightly mozconfig branding to release (currently it's beta) as per discussion in irc with bhearsum, who checked with mfinkle.
Attachment #539188 - Flags: review?(lsblakk) → review+
Per mfinkle, we're using official branding for the on-change builds here: [10:02] <mfinkle> where we use beta branding for mozilla-beta [10:02] <mfinkle> I suppose we should sue release branding for mozilla-release [10:02] <bhearsum> ah Landed on default.
Attachment #539188 - Attachment is obsolete: true
Attachment #539192 - Flags: checked-in+
This hit production. I had to land one bustage fix, because I forgot to copy over the 10.5 mac debug mozconfig. Otherwise, it's smooth so far.
I'm pretty sure we're all done here now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
I think we should disable XULRunner on this branch if there are no Firefox nightlies, and also the blocklist updates builder.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Both of your suggestions make sense to me, Nick.
Attachment #540135 - Flags: review?(nrthomas)
Attachment #540135 - Flags: review?(nrthomas) → review+
Comment on attachment 540135 [details] [diff] [review] disable xulrunner, blocklist update Landed on default.
Attachment #540135 - Flags: checked-in+
This made it to production today. We're done here, again.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 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.

Attachment

General

Created:
Updated:
Size: