Closed Bug 865814 Opened 12 years ago Closed 11 years ago

start using "beta" mozconfigs for beta builds, separate from "release" mozconfigs

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox23+ fixed)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox23 + fixed

People

(Reporter: Gavin, Assigned: bhearsum)

References

Details

Attachments

(1 file)

switch mozconfigs in mozilla-beta template
(deleted), patch
rail
: review+
bhearsum
: checked-in+
Details | Diff | Splinter Review
To support bug 853071, we'll need to start using separate (but nearly identical) mozconfigs for beta and release builds.
We need this bug to support bug 853071 in release automation. 23.0b1 will be the first release with that code.
tracking-firefox23: --- → ?
Assignee: nobody → bhearsum
Status: NEW → ASSIGNED
Attachment #757475 - Flags: review?(rail)
Comment on attachment 757475 [details] [diff] [review] switch mozconfigs in mozilla-beta template verified that the new mozconfigs are only in mozilla-aurora atm, not in mozilla-beta. We'll need to land this patch as a part of merge day or just before 23.0b1 build. Ben, can you make sure that this bug blocks either the merge day bug or the 23.0b1 tracking bug?
Attachment #757475 - Flags: review?(rail) → review+
Blocks: 842865
Whiteboard: [no-nag]
Blocks: 882720
Attachment #757475 - Flags: checked-in+
In production
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
status-firefox23: --- → fixed
Whiteboard: [no-nag]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: