972615 - add esr24 relbranches to gecko-dev

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Aki Sasaki (not active)]

For Tor.

Comment 1

[Aki Sasaki (not active)]

Attachment: esr24

Comment 2

[Hal Wine [:hwine] use NI!]

Comment on attachment 8375858 [details] [diff] [review]
esr24

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

One nit - r+ whether you make that change or not.

::: configs/vcs_sync/beagle.py
@@ +388,5 @@
>              "branches": {
>                  "default": "esr24",
>              },
> +            "branch_regexes": {
> +                "^GECKO[0-9]+esr_[0-9]+_RELBRANCH",

Since we anchor at the front of the expression (^), shouldn't we anchor at the end as well? ($)

Comment 3

[Aki Sasaki (not active)]

Comment on attachment 8375858 [details] [diff] [review]
esr24

http://hg.mozilla.org/build/mozharness/rev/5ec7c421defd

Comment 4

[Aki Sasaki (not active)]

Seeing the ESR 24 relbranches in gecko-dev, e.g.:
https://github.com/mozilla/gecko-dev/tree/GECKO2430esr_2014013111_RELBRANCH

Mike: a) sorry for the delay, and b) sorry for the imperfect fix.

In the not-too-distant future, we should have mapper available to the public, which will allow people to determine git shas from hg shas and vice versa (bug 847640).  Longer term we'd like to move away from moving hg tags in our release process, which will allow for converting them without those issues.

Comment 5

[Aki Sasaki (not active)]

Oh, also followup fix: http://hg.mozilla.org/build/mozharness/rev/452f8b450cb0