Kill mozilla-b2g28_v1_3 after Sep 2 merge day

RESOLVED FIXED

Status

Release Engineering
General Automation
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(5 attachments)

(Assignee)

Description

3 years ago
+++ This bug was initially created as a clone of Bug #1014287 +++

per Bhavana, we are going to kill mozilla-b2g28_v1_3, but not mozilla-b2g28_v1_3t. The go is expected on Sep 3rd, Wed.

We can land the patches after bug 1029851 is fixed. It would be better to prep patches on top of the patches in bug 1029851 to avoid bitrots.


Important:

* Leave branch/repo open for commits
* continue pushing any commits to the partner visible repos on git.m.o

Prior work:
* bug 948521
* bug 920319
* bug 875164
* bug 1014287
* bug 875164
(Assignee)

Updated

3 years ago
Assignee: nobody → rail
(Assignee)

Updated

3 years ago
Summary: mozilla-b2g28_v1_3 after Sep 2 merge day → Kill mozilla-b2g28_v1_3 after Sep 2 merge day
Does this include mozilla-b2g28_v1_3t as well?
Flags: needinfo?(bbajaj)
(Assignee)

Comment 2

3 years ago
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #1)
> Does this include mozilla-b2g28_v1_3t as well?

Not yet, mozilla-b2g28_v1_3t hasn't been shipped/released yet.
(In reply to Rail Aliiev [:rail] from comment #2)
> (In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #1)
> > Does this include mozilla-b2g28_v1_3t as well?
> 
> Not yet, mozilla-b2g28_v1_3t hasn't been shipped/released yet.

It actually just did a few days back in INdia, but I was skeptical if we may need more changes to land here or new partners shipping from this branch. I am confirming with folks who manage this branch for a sure shot confirmation, but until then lets keep it alive.
Flags: needinfo?(bbajaj)
(Assignee)

Comment 4

3 years ago
Created attachment 8483663 [details] [diff] [review]
kill_v1.3-mozharness.diff

I left v1.3 in the following places:

configs/vcs_sync/l10n.py
configs/vcs_sync/beagle.py

Let me know if we should stop vcssync for those as well.
Attachment #8483663 - Flags: review?(hwine)
(Assignee)

Comment 5

3 years ago
Created attachment 8483666 [details] [diff] [review]
kill_v1.3-tools.diff
Attachment #8483666 - Flags: review?(nthomas)
(Assignee)

Comment 6

3 years ago
Created attachment 8483668 [details] [diff] [review]
kill_v1.3-buildbot-configs.diff
Attachment #8483668 - Flags: review?(nthomas)
(Assignee)

Comment 7

3 years ago
Created attachment 8483670 [details] [diff] [review]
kill_v1.3-puppet.diff
Attachment #8483670 - Flags: review?(hwine)
Comment on attachment 8483663 [details] [diff] [review]
kill_v1.3-mozharness.diff

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

I don't think we want to change gecko-git.py for the same reason we're not touching legacy -- if someone commits to that branch, it should be visible. I believe that is a requirement to handle any potential chemspill situation (where the builders may not be needed).

If you agree, then r+ without that change. Otherwise, let's discuss
Attachment #8483663 - Flags: review?(hwine) → review+
Comment on attachment 8483670 [details] [diff] [review]
kill_v1.3-puppet.diff

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

lgtm
Attachment #8483670 - Flags: review?(hwine) → review+
Attachment #8483666 - Flags: review?(nthomas) → review+
Attachment #8483668 - Flags: review?(nthomas) → review+
(Assignee)

Comment 10

3 years ago
Comment on attachment 8483668 [details] [diff] [review]
kill_v1.3-buildbot-configs.diff

https://hg.mozilla.org/build/buildbot-configs/rev/109a8f07353d
Attachment #8483668 - Flags: checked-in+
(Assignee)

Comment 11

3 years ago
Created attachment 8484131 [details] [diff] [review]
tbpl-kill-v1.3.diff
Attachment #8484131 - Flags: review?(ryanvm)
Comment on attachment 8484131 [details] [diff] [review]
tbpl-kill-v1.3.diff

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

Patch looks fine, but I'm a bit ambivalent about whether we should be dropping it from TBPL now or wait until the 30 day data retention period is over.
Attachment #8484131 - Flags: review?(ryanvm) → review+
Merged to production, and deployed.
(Assignee)

Comment 14

3 years ago
Comment on attachment 8483666 [details] [diff] [review]
kill_v1.3-tools.diff

https://hg.mozilla.org/build/tools/rev/9601a3e9fde0
Attachment #8483666 - Flags: checked-in+
(Assignee)

Comment 15

3 years ago
Comment on attachment 8483670 [details] [diff] [review]
kill_v1.3-puppet.diff

remote:   https://hg.mozilla.org/build/puppet/rev/7e762c82236b
remote:   https://hg.mozilla.org/build/puppet/rev/c4138a46f730
Attachment #8483670 - Flags: checked-in+
(Assignee)

Comment 16

3 years ago
Comment on attachment 8483663 [details] [diff] [review]
kill_v1.3-mozharness.diff

remote:   https://hg.mozilla.org/build/mozharness/rev/3cf5602fce51
remote:   https://hg.mozilla.org/build/mozharness/rev/4682779d3d2d
Attachment #8483663 - Flags: checked-in+
(Assignee)

Comment 17

3 years ago
Comment on attachment 8484131 [details] [diff] [review]
tbpl-kill-v1.3.diff

https://hg.mozilla.org/webtools/tbpl/rev/d6f5de0c4b2f
Attachment #8484131 - Flags: checked-in+
(Assignee)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Depends on: 1071160
(In reply to Rail Aliiev [:rail] from comment #17)
> Comment on attachment 8484131 [details] [diff] [review]
> tbpl-kill-v1.3.diff
> 
> https://hg.mozilla.org/webtools/tbpl/rev/d6f5de0c4b2f

In production :)
You need to log in before you can comment on or make changes to this bug.