Closed Bug 1030240 Opened 11 years ago Closed 11 years ago

Add new tree {mozilla,comm}-esr31 to TBPL

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: massimo, Assigned: massimo)

References

Details

Attachments

(1 file, 1 obsolete file)

as in bug 808017, needs to be deployed when we have real builds.
Attachment #8445992 - Flags: review?(emorley)
Comment on attachment 8445992 [details] [diff] [review] {mozilla,comm}-esr31 entries.patch Review of attachment 8445992 [details] [diff] [review]: ----------------------------------------------------------------- Please make the same changes to mcmerge/js/Config.js as well.
Attachment #8445992 - Flags: review?(emorley) → review-
updated mcmerge/js/Config.js as well.
Attachment #8445992 - Attachment is obsolete: true
Attachment #8446019 - Flags: review?(ryanvm)
Comment on attachment 8446019 [details] [diff] [review] {mozilla,comm}-esr31 entries.patch Review of attachment 8446019 [details] [diff] [review]: ----------------------------------------------------------------- We typically list the trees in descending order, so please put the esr31 entries above esr24. Otherwise, looks good with the one other comment addressed. ::: mcmerge/js/Config.js @@ +274,5 @@ > + "comm-esr31": { > + repo: "releases/comm-esr31", > + unconditionalFlag: false, > + trackedTree: true, > + synonyms: ["releases/comm-esr31", "comm-esr31", "comm-release"] I have a feeling the comm-release on this line is going to confuse things since it's already on the esr24 line above as well. Let's leave it off for now.
Attachment #8446019 - Flags: review?(ryanvm) → review+
Depends on: 1037175
In production :)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Assignee: nobody → mgervasini
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: