1037107 - create mozilla-b2g32_v2_0 branch

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Comment 1

[Aki Sasaki (not active)]

Attachment: b2g_tag

Comment 2

[Aki Sasaki (not active)]

Comment on attachment 8457683 [details] [diff] [review]
b2g_tag

http://hg.mozilla.org/build/mozharness/rev/34c5d8272f03

Comment 3

[Aki Sasaki (not active)]

Attachment: b2g32_configs

Comment 4

[Aki Sasaki (not active)]

Attachment: b2g32_custom

Comment 5

[Aki Sasaki (not active)]

Attachment: b2g32_tools

Comment 6

[Aki Sasaki (not active)]

Attachment: b2g32_tbpl

Comment 7

[Aki Sasaki (not active)]

Attachment: b2g32_beagle

Comment 8

[Aki Sasaki (not active)]

Comment on attachment 8457705 [details] [diff] [review]
b2g32_tbpl

https://hg.mozilla.org/webtools/tbpl/rev/35fc0b71256f

Comment 9

[Pete Moore [:pmoore][:pete]]

Comment on attachment 8457707 [details] [diff] [review]
b2g32_beagle

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

Nice work Aki.

::: configs/vcs_sync/beagle.py
@@ +254,5 @@
> +            "tag_config": {
> +                "tag_regexes": [
> +                    "^B2G_",
> +                ],
> +            },

This tag_config is the same as the tag_config below (lines 266 to 270). I think this isn't needed, because I believe if it is not provided by the specific target, it is taken from the generic cross-target tag_config section (http://hg.mozilla.org/build/mozharness/file/7e18e11a38be/scripts/vcs-sync/vcs_sync.py#l500).

However, it should not hurt, and it would be consistent with the other branches in this config file - but I believe it may be redundant to define it in both places.

Comment 10

[Aki Sasaki (not active)]

(In reply to Pete Moore [:pete][:pmoore] from comment #9)
> ::: configs/vcs_sync/beagle.py
> @@ +254,5 @@
> > +            "tag_config": {
> > +                "tag_regexes": [
> > +                    "^B2G_",
> > +                ],
> > +            },
> 
> This tag_config is the same as the tag_config below (lines 266 to 270). I
> think this isn't needed, because I believe if it is not provided by the
> specific target, it is taken from the generic cross-target tag_config
> section
> (http://hg.mozilla.org/build/mozharness/file/7e18e11a38be/scripts/vcs-sync/
> vcs_sync.py#l500).
> 
> However, it should not hurt, and it would be consistent with the other
> branches in this config file - but I believe it may be redundant to define
> it in both places.

Aha.  Sure, up to you.  Might be a safety net, might be a pain keeping them in sync; I think I agree it's probably the latter.

Comment 11

[Aki Sasaki (not active)]

Attachment: graphs

Looks complete based on https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Steps#Add_to_Graphs .

Comment 12

[Aki Sasaki (not active)]

Comment on attachment 8457707 [details] [diff] [review]
b2g32_beagle

Committed without the duplicate tag_config.
https://hg.mozilla.org/build/mozharness/rev/c5821474653e

Comment 13

[Aki Sasaki (not active)]

Comment on attachment 8457701 [details] [diff] [review]
b2g32_custom

https://hg.mozilla.org/build/buildbotcustom/rev/433adf0b3644

Comment 14

[Aki Sasaki (not active)]

Comment on attachment 8457700 [details] [diff] [review]
b2g32_configs

https://hg.mozilla.org/build/buildbot-configs/rev/7707449277f1

Comment 15

[Aki Sasaki (not active)]

Comment on attachment 8457702 [details] [diff] [review]
b2g32_tools

https://hg.mozilla.org/build/tools/rev/a5d1390ed38a

Comment 16

[Hal Wine [:hwine] use NI!]

Comment on attachment 8458122 [details] [diff] [review]
graphs

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

lgtm

Comment 17

[Aki Sasaki (not active)]

Attachment: in-tree-l10n

Comment 18

[Aki Sasaki (not active)]

Attachment: in-tree-channel

Since bug 1022907 isn't fixed yet.

Comment 19

[Aki Sasaki (not active)]

Attachment: bump_bb-c_versions

Comment 20

[Hal Wine [:hwine] use NI!]

Comment on attachment 8458447 [details] [diff] [review]
bump_bb-c_versions

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

lgtm

Comment 21

[Ryan VanderMeulen [:RyanVM]]

(In reply to Aki Sasaki [:aki] from comment #8)
> https://hg.mozilla.org/webtools/tbpl/rev/35fc0b71256f

In production :)

Comment 22

[Aki Sasaki (not active)]

In production.

Comment 23

[Aki Sasaki (not active)]

Comment on attachment 8458122 [details] [diff] [review]
graphs

http://hg.mozilla.org/graphs/rev/632a9d16cb0d

Comment 24

[Aki Sasaki (not active)]

Attachment: disable_dolphin

It looks like we were intentionally only building dolphin on 1.4, like we're only building Tarako on 1.3t.  Re-disabling...

Comment 25

[Aki Sasaki (not active)]

Comment on attachment 8458445 [details] [diff] [review]
in-tree-channel

https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/e5db66301250

Comment 26

[Aki Sasaki (not active)]

Comment on attachment 8458443 [details] [diff] [review]
in-tree-l10n

https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/bcd1e9db532a

Comment 27

[Aki Sasaki (not active)]

Comment on attachment 8458447 [details] [diff] [review]
bump_bb-c_versions

http://hg.mozilla.org/build/buildbot-configs/rev/ea1dd17b4a35

Comment 28

[Aki Sasaki (not active)]

Comment on attachment 8458921 [details] [diff] [review]
disable_dolphin

http://hg.mozilla.org/build/buildbot-configs/rev/3d0e0896b4e2

Comment 29

[Aki Sasaki (not active)]

In production.

Comment 30

[Aki Sasaki (not active)]

Er,
https://bugzilla.mozilla.org/show_bug.cgi?id=1017923#c32

Comment 31

[Aki Sasaki (not active)]

https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Steps#Push_to_mozilla-b2gXX_vX_X_.3F

Comment 32

[Aki Sasaki (not active)]

dev-b2g:
As of today's uplift, the Gecko side of B2G v2.0 now lives on the
mozilla-b2g32_v2_0 branch, *NOT* mozilla-aurora. Patches that are
blocking-b2g:2.0+ should be landed there now. For more information, see
the page below which always contains the latest information.
https://wiki.mozilla.org/Release_Management/B2G_Landing#v2.0.0

As a reminder, B2G v2.1 development remains on mozilla-central through
the duration of the Gecko 34 development cycle due to end on Sept 1, so
there is no change for where v2.1 patches are to land.

Comment 34

[Aki Sasaki (not active)]

http://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/00f4b3a7046f
https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Merge_Duty/Steps&diff=998816&oldid=998812