Comment on attachment 8453972 [details] [diff] [review] bump_release_version https://hg.mozilla.org/build/buildbot-configs/rev/d3b916ef173d

#r-d convo that resulted in bug 1038282: [10:43] <aki> Sylvestre: sw is shipping in 31 ? [10:43] <aki> Pike: ^^ [10:44] <Sylvestre> aki, I haven't seen information about that :/ [10:45] <aki> Sylvestre: https://bugzilla.mozilla.org/show_bug.cgi?id=1019151 turned it off for 30; unclear whether it's ready to ship [10:47] <Sylvestre> I guess it is the same as in 30 [10:47] <aki> "142 missing, 148 obsolete" seems bad, but i also see "1 error(s), 2701 missing, 74 obsolete" https://l10n.mozilla.org/shipping/about-milestone/fx31_beta_b9 [10:48] <aki> ok, i'll try without sw [10:51] <Pike> yeah, not [10:51] <Pike> aki: want a bug on that? [10:51] <aki> Pike: i'm fine with irc. hsb is shipping? [10:52] <aki> also, is there a way for relman to know this ahead of merge day? [10:53] <Pike> just filed bug 1038282 for paper work either way [10:54] <aki> ty [10:54] <Pike> I think in general this should the "Final locale check with :Pike before we build RC candidate next week" last wednesday on the release calendar [10:54] <Pike> that process didn't work out well, though Keeping the "Get the list of l10n locales to remove from release management." line in https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Steps#Perform_mozilla-beta_-.3E_mozilla-release_migration

Found some changes I needed to make in gecko_migration.py for the beta->release migration. Should be a one-time patch.

Comment on attachment 8455498 [details] [diff] [review] migration_script_release http://hg.mozilla.org/build/mozharness/rev/c5509ad117fe

Another one-time fix. Basically, change the http://hg.mozilla.org/releases/mozilla-beta/rev/6befadcaa685 comment to only say "Tagging mozilla-beta ..." instead of "Tagging /src/.../mozilla-beta ..."

Comment on attachment 8455532 [details] [diff] [review] beta_tag_fix https://hg.mozilla.org/build/mozharness/rev/b95ae3e414a7

Oops, https://bugzilla.mozilla.org/attachment.cgi?id=8458447&action=edit should have been in this bug.

Not sure what I think of the build_localconfig.py bit. In a way it was a pain to remember, and in a way this patch is a little ugly.

Per https://wiki.mozilla.org/ReleaseEngineering/Merge_Duty/Steps#Update_l10n_vcs-sync .

Comment on attachment 8458475 [details] [diff] [review] new_vcs-sync_l10n Review of attachment 8458475 [details] [diff] [review]: ----------------------------------------------------------------- r+ with comments removed (and if v2_1 does not yet need to be added) ::: configs/vcs_sync/l10n.py @@ +89,2 @@ > # MERGE DAY switch to the below hg_url on 2014-07-21 > # 'hg_url': 'https://hg.mozilla.org/releases/gaia-l10n/v2_0/%(locale)s', The updated hg_url is fine, but the comments in lines 89 and 90 need to be removed. I haven't yet checked the merge day docs - but I guess adding v2_1 comes later, and then we point v2_1 to https://hg.mozilla.org/gaia-l10n/%(locale)s - or does that need to be done at the same time as this change?

(In reply to Pete Moore [:pete][:pmoore] from comment #12) > ::: configs/vcs_sync/l10n.py > @@ +89,2 @@ > > # MERGE DAY switch to the below hg_url on 2014-07-21 > > # 'hg_url': 'https://hg.mozilla.org/releases/gaia-l10n/v2_0/%(locale)s', > > The updated hg_url is fine, but the comments in lines 89 and 90 need to be > removed. Good catch. > I haven't yet checked the merge day docs - but I guess adding v2_1 comes > later, and then we point v2_1 to https://hg.mozilla.org/gaia-l10n/%(locale)s > - or does that need to be done at the same time as this change? 2.1 is on master, so it's called 'master' til 6 weeks from now. At that point gecko goes to mozilla-aurora and we create a v2_1 from gaia-l10n, and then 12 weeks from now we pull v2_1 from releases/gaia-l10n/v2_1, unless the process changes again.

Comment on attachment 8458511 [details] [diff] [review] legacy_vcs-sync_l10n lgtm, and applying the patch seems to be consistent: = config diff = == before applying == * number of l10n hgrc files r!ls *l10n*/hgrc | wc 129 129 3977 == after applying == * number of l10n hgrc files r!ls *l10n*/hgrc | wc 129 129 3977 * number of files in patch (2x # repos): r! grep -c ^diff /tmp/legacy_vcs-sync_l10n.txt 148 * number of l10n config files with a renameremotev20defaultbranchto line: r! grep -l renameremotev20defaultbranchto *l10n*/config | wc 74 74 2199 * number of l10n config files with v2_0 in remotes_to_pull r! grep remotes_to_pull *l10n*/hgrc | grep -cw v2_0 74

Comment on attachment 8458475 [details] [diff] [review] new_vcs-sync_l10n https://hg.mozilla.org/build/mozharness/rev/fe63e782cbe2

(In reply to Aki Sasaki [:aki] from comment #15) > Comment on attachment 8458475 [details] [diff] [review] > new_vcs-sync_l10n > > https://hg.mozilla.org/build/mozharness/rev/fe63e782cbe2 New vcs-sync l10n isn't live yet, so not merging atm. In later merge days the timing on this will be more important, but not critical until we start pulling l10n from git in our b2g builds.

Comment on attachment 8458511 [details] [diff] [review] legacy_vcs-sync_l10n http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/cd17f7ccea8f

bumped gecko versions in http://hg.mozilla.org/build/buildbot-configs/rev/ea1dd17b4a35

Comment on attachment 8458460 [details] [diff] [review] disable-aurora http://hg.mozilla.org/build/buildbot-configs/rev/89792b3302cd

In production.

This isn't live yet, but it's good practice and may help avoid breaking pmoore's staging.

Comment on attachment 8459702 [details] [diff] [review] pause_gecko_git_legacy Review of attachment 8459702 [details] [diff] [review]: ----------------------------------------------------------------- lgtm

Comment on attachment 8459704 [details] [diff] [review] pause_new_vcs-sync http://hg.mozilla.org/build/mozharness/rev/dfcfae9a1bc6

Comment on attachment 8459702 [details] [diff] [review] pause_gecko_git_legacy https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/0a96492cc05b

With less hardcode and more branches for release_to_esr

Comment on attachment 8459758 [details] [diff] [review] fix_migration maybe pull_by_revision() and make revision mandatory?

Comment on attachment 8459758 [details] [diff] [review] fix_migration (In reply to Rail Aliiev [:rail] from comment #28) > Comment on attachment 8459758 [details] [diff] [review] > fix_migration > > maybe pull_by_revision() and make revision mandatory? Per IRC, making revision mandatory would break beta_to_release and release_to_esr. http://hg.mozilla.org/build/mozharness/rev/09e438ee911a

Needed to actually get the migration working from aurora->beta.

Comment on attachment 8459798 [details] [diff] [review] get_merge_day_working https://hg.mozilla.org/build/mozharness/rev/042ee7510b2f

Landed gaia_l10n.sh in braindump for getting the gaia-l10n v2_0 repos in sync. https://hg.mozilla.org/build/braindump/rev/2e7c16ba5c9c I got "WARNING releases/gaia-l10n/v2_0/es is newer!" for https://hg.mozilla.org/releases/gaia-l10n/v2_0/es/rev/895d5487bc41 ; the comment says it's 2.0 specific so no worries there. Updating docs...

Comment on attachment 8459879 [details] [diff] [review] legacy_2.0_tools Review of attachment 8459879 [details] [diff] [review]: ----------------------------------------------------------------- lgtm

Comment on attachment 8459880 [details] [diff] [review] legacy_2.0_configs Review of attachment 8459880 [details] [diff] [review]: ----------------------------------------------------------------- lgtm

Comment on attachment 8459879 [details] [diff] [review] legacy_2.0_tools https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/930bbbe21271

Comment on attachment 8459880 [details] [diff] [review] legacy_2.0_configs https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/9f59333750d9

Comment on attachment 8459878 [details] [diff] [review] enable_new_vcs-sync https://hg.mozilla.org/build/mozharness/rev/84b3c50018f7

Followup fix to legacy keep_updated: https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/a96a1d31e6ea woot http://git.mozilla.org/?p=releases/gecko.git;a=shortlog;h=refs/heads/v2.0

We used to have RELEASE_BASE_* after merge day but we don't have RELEASE_BASE_20140721. Is that expected? Thanks

Yes, the naming has changed to match aurora and beta. https://hg.mozilla.org/releases/mozilla-beta/rev/1772e55568e4 FIREFOX_RELEASE_31_BASE

Oops, forgot to land: http://hg.mozilla.org/build/mozharness/rev/c9c14b7f685b