Migrate bumpFiles patch to comm-esr17/comm-esr10

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
5 months ago

People

(Reporter: jhopkins, Assigned: jhopkins)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

6 years ago
We need to port this patch http://hg.mozilla.org/build/buildbot-configs/raw-rev/c870fc478468 to ESR17 when standard8 is ready to take it.

This is not part of the merge week work.
Blocks: 796975
We should do this before the releases today if we can, then we won't be dependent on the relbranch.
Created attachment 682418 [details] [diff] [review]
bumpFiles for esr17
Attachment #682418 - Flags: review?(bhearsum)
Comment on attachment 682418 [details] [diff] [review]
bumpFiles for esr17

Review of attachment 682418 [details] [diff] [review]:
-----------------------------------------------------------------

Please don't modify the non-template files, actually. It'll get updated when the release gets started. r=me for the template part.
Attachment #682418 - Flags: review?(bhearsum) → review+
Created attachment 697440 [details] [diff] [review]
Same for comm esr10

Same for ESR 10, to make the go for the release easier.
Attachment #697440 - Flags: review?(bhearsum)
Blocks: 810328
Attachment #697440 - Flags: review?(bhearsum) → review+
OS: Mac OS X → All
Hardware: x86 → All
Summary: Migrate bumpFiles patch to comm-esr17 → Migrate bumpFiles patch to comm-esr17/comm-esr10
(Assignee)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(In reply to Mark Banner (:standard8) from comment #6)
> Comment on attachment 697440 [details] [diff] [review]
> Same for comm esr10
> 
> http://hg.mozilla.org/build/buildbot-configs/rev/89dbc8d25a22

I transplanted this to production to make sure we don't miss it when we start builds today.

Comment 8

6 years ago
in production
Product: mozilla.org → Release Engineering
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.