Closed Bug 1123369 Opened 9 years ago Closed 9 years ago

Tracking bug for 30-March-2015 migration work

Categories

(Release Engineering :: Release Requests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: jlund)

References

Details

Attachments

(2 files, 2 obsolete files)

+++ This bug was initially created as a clone of Bug #1123367 +++
Depends on: 1120969
No longer depends on: 1117241
Assignee: nobody → jlund
Depends on: 1144102
preliminary review.

rollout plan before migration script call for m-b -> m-r:

   on Monday, March 23rd:
       1) land this patch
       2) reconfig
Attachment #8580307 - Flags: review?(rail)
preliminary review.

rollout plan before migration script call for m-c -> m-a -> m-b:

   on Monday, March 23rd:
       1) land this patch
       2) reconfig
Attachment #8580308 - Flags: review?(rail)
> rollout plan before migration script call for m-c -> m-a -> m-b:
> 
>    on Monday, March 23rd:

typo, this will be done on the following monday, March 30th.
note, this release cycle is a happening a week earlier than our regular 6 week cadence
Summary: Tracking bug for 06-Apr-2015 migration work → Tracking bug for 30-March-2015 migration work
hrm, I need to sanity check this:

rail, in lawernce's email regarding changes to release dates, I see the following:

"""
Firefox 37
- Beta: reduced to 5 weeks (this means 2 fewer betas in the cycle)
- Release date change: from April 7, 2015, to March 31, 2015

Firefox 38
- Aurora / Dev Edition: reduced to 5 weeks
- Release date change: from May 19, 2015, to May 12, 2015

Firefox 39
- Nightly: reduced to 5 weeks
- Beta: extended to 7 weeks
- Release date unchanged

Firefox 40
- Aurora: extended to 7 weeks
- Release date unchanged

Firefox 41
- Nightly: extended to 7 weeks
- Release date unchanged

Questions, concerns, support, and general feedback is welcome.
"""

what is unclear to me here is how it suggests only beta and release schedules are changing rather than every release branch going back by 1 week.

so, are we moving the entire merge schedule back by 1 week
m-b -> m-r merge: changed from March 30th -> March 23rd
m-a -> m-b, m-c -> m-a merge: change from April 6th -> March 30th

Or, are we only changing beta and release merge dates:
m-b -> m-r merge: changed from March 30th -> March 23rd
m-a -> m-b merge: change from April 6th -> March 30th
m-c -> m-a merge: stays on schedule for April 6th
Flags: needinfo?(rail)
Attachment #8580307 - Flags: review?(rail) → review+
Attachment #8580308 - Flags: review?(rail) → review+
This is from lmandel's email:

In case you not clear on the two different merge requests that will come in, here are the two requests that you should expect to receive:

Mon, Mar 23 m-b -> m-r - Request will come from me (I'm managing 37)
Mon, Mar 30 m-a -> m-b, m-c -> m-a - Request will come from Sylvestre (he's managing 38)
Flags: needinfo?(rail)
I will be on-line at 0630 PDT tomorrow.

Monday, March 23 merge duty tasks: https://gist.github.com/lundjordan/b66bff783b6853e024f6#day-7---release-merge-day
Comment on attachment 8580307 [details] [diff] [review]
150319_mergeduty_m-r_gecko_version_bump-bbotcfgs.patch

on default: https://hg.mozilla.org/build/buildbot-configs/rev/2f6a581c1f05
Attachment #8580307 - Flags: checked-in+
Depends on: 1144475
Comment on attachment 8580308 [details] [diff] [review]
150319_mergeduty_m-b_m-a_m-c_comm_gecko_version_bump-bbotcfgs.patch

default:   https://hg.mozilla.org/build/buildbot-configs/rev/9678c4380ac4
Attachment #8580308 - Flags: checked-in+
status: all work for this has been done bar:
  https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty#Post_merge_day

hwine has agreed to keep an eye out for the un-throttle email as I am on STAT tomorrow and away until Sunday night.

Once this is done, this bug can be closed
Depends on: 1151498
Unthrottle Auroroa work completed
Depends on: 1151153
No longer depends on: 1144475
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
ba-bump!

we are migrating m-b -> m-r early
Attachment #8593706 - Flags: review?(rail)
Comment on attachment 8593706 [details] [diff] [review]
150416_may_mergeduty_m-r_gecko_version_bump-bbotcfgs.patch

doh! wrong migrating tracking bug ;)
Attachment #8593706 - Attachment is obsolete: true
Attachment #8593706 - Flags: review?(rail)
Attachment #8891306 - Attachment is obsolete: true
Attachment #8891306 - Flags: review?(rgarbas)
mea culpa - wrong migration tracking bug :)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: