Closed
Bug 875164
Opened 12 years ago
Closed 10 years ago
kill b2g18 + b2g18_v1_1_0_hd
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: mozilla)
References
Details
Attachments
(7 files, 2 obsolete files)
13.82 KB,
patch
|
Details | Diff | Splinter Review | |
1.15 KB,
patch
|
Details | Diff | Splinter Review | |
6.98 KB,
patch
|
Details | Diff | Splinter Review | |
75.17 KB,
patch
|
Details | Diff | Splinter Review | |
2.84 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
59.10 KB,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
564 bytes,
patch
|
rail
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
No branch for b2g 1.1.0 (bug 850495 comment 6), so undo the preparations.
This includes, at a minimum:
- turning off vcs-sync coversion
- having repos created in bug 850482 deleted
- revert changes from bug 850495 attachment 735404 [details] [diff] [review]
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•11 years ago
|
Blocks: 943080
Flags: needinfo?(hwine)
Summary: tear down b2g 1.1.0 repos → turn off b2g 1.1 when 1.3 ships
Assignee | ||
Comment 2•11 years ago
|
||
Per :bajaj, we will EOL these branches during the March 17 merge cycle.
Comment 3•11 years ago
|
||
[12:46] <rail> bajaj_: hey, just to double check, we are going to stop building/testing mozilla-b2g18 and mozilla-b2g18_v1_1_0_hd after the next merge day (in 2 weeks). is this correct?
[12:47] <bajaj_> rail: yes, I'll send a note out about the EOL for that branch in a while!
Comment 5•11 years ago
|
||
Attachment #8389822 -
Flags: review?(hwine)
Comment 6•11 years ago
|
||
Attachment #8389823 -
Flags: review?(hwine)
Comment 7•11 years ago
|
||
Comment on attachment 8389823 [details] [diff] [review]
merge-day-tools.diff
need to kill moar stuff
Attachment #8389823 -
Flags: review?(hwine)
Reporter | ||
Comment 8•11 years ago
|
||
Comment on attachment 8389822 [details] [diff] [review]
merge-day-mozharness.diff
Review of attachment 8389822 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm, however we may want/need to land the two vcs-sync configs separately. We should review timing before the merge.
Attachment #8389822 -
Flags: review?(hwine) → review+
Reporter | ||
Updated•11 years ago
|
Attachment #8389823 -
Flags: review+
Comment 9•11 years ago
|
||
* kills b2g18 and b2g18_1_* branches
* kills android-noion platform which was b2g18 only
* kills loops with gecko_version < 24
* removes unused checks against mozilla-esr24 in b2g_config.py
* fixes some b2g18 related comments
* makes a double shot espresso :)
Attachment #8389981 -
Flags: review?(nthomas)
Attachment #8389981 -
Flags: review?(catlee)
Comment 10•11 years ago
|
||
Removes android-noion (b2g18 only)
Attachment #8389983 -
Flags: review?(hwine)
Comment 11•11 years ago
|
||
+ android-noion
Attachment #8389823 -
Attachment is obsolete: true
Attachment #8389984 -
Flags: review?(hwine)
Comment 12•11 years ago
|
||
refreshed, conflicts resolved
Attachment #8389981 -
Attachment is obsolete: true
Attachment #8389981 -
Flags: review?(nthomas)
Attachment #8389981 -
Flags: review?(catlee)
Attachment #8390154 -
Flags: review?(nthomas)
Attachment #8390154 -
Flags: review?(catlee)
Comment 13•11 years ago
|
||
Comment on attachment 8389983 [details] [diff] [review]
kill-b2g18-buildbotcustom.diff
Per Bhavana we need to keep b2g18 around until we *ship* 1.3. I'll leave the patches as a reference.
Attachment #8389983 -
Flags: review?(hwine)
Updated•11 years ago
|
Attachment #8389984 -
Flags: review?(hwine)
Updated•11 years ago
|
Attachment #8390154 -
Flags: review?(nthomas)
Attachment #8390154 -
Flags: review?(catlee)
Updated•11 years ago
|
Attachment #8389822 -
Flags: review+
Assignee | ||
Comment 14•11 years ago
|
||
Verbal "go" from Bhavana.
Blocks: 824169
Summary: turn off b2g 1.1 when 1.3 ships → kill b2g18 + b2g18_v1_1_0_hd
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 15•11 years ago
|
||
I think I have to land this before my test-masters will work =(
Attachment #8427234 -
Flags: review?(rail)
Comment 16•11 years ago
|
||
Comment on attachment 8427234 [details] [diff] [review]
b2g18-tools
lgtm,
I'd rather land all patches at once to avoid reconfig issues.
You can use your local copy of tools to test configs/custom like this:
python setup-master.py --test --masters-json ../tools/buildfarm/maintenance/production-masters.json --error-logs
Attachment #8427234 -
Flags: review?(rail) → review+
Assignee | ||
Comment 17•11 years ago
|
||
Attachment #8427269 -
Flags: review?(rail)
Assignee | ||
Comment 18•11 years ago
|
||
Attachment #8427270 -
Flags: review?(rail)
Comment 19•11 years ago
|
||
Comment on attachment 8427270 [details] [diff] [review]
b2g18-custom
Can you also kill "android-noion" in process/factory.py?
Attachment #8427270 -
Flags: review?(rail) → review+
Comment 20•11 years ago
|
||
Comment on attachment 8427269 [details] [diff] [review]
b2g18-config
as mentioned on IRC, remove "b2g18" from setup-master.py and we are good to go!
Attachment #8427269 -
Flags: review?(rail) → review+
Assignee | ||
Comment 21•11 years ago
|
||
Comment on attachment 8427270 [details] [diff] [review]
b2g18-custom
https://hg.mozilla.org/build/buildbotcustom/rev/30a34cb9a554
Attachment #8427270 -
Flags: checked-in+
Assignee | ||
Comment 22•11 years ago
|
||
Comment on attachment 8427269 [details] [diff] [review]
b2g18-config
https://hg.mozilla.org/build/buildbot-configs/rev/a84e1ec37009
Attachment #8427269 -
Flags: checked-in+
Assignee | ||
Comment 23•11 years ago
|
||
Comment on attachment 8427234 [details] [diff] [review]
b2g18-tools
https://hg.mozilla.org/build/tools/rev/7f17d9a61982
Attachment #8427234 -
Flags: checked-in+
Comment 24•10 years ago
|
||
Merged and deployed to production.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•