Before 09dec, we'll be needing automation support for b2g v1.3, so that v1.4 work can start landing on master. Let's get the branches, repos, etc., created ahead of time. Note: to start with, the new v1.3 branch should be kept closed to developer-checkins until we get the official word to open v1.3 branch for checkins. For reference, bug#913992 tracked setup for v1.2.0, bug#850481 tracked setup for v1.1.0, and bug#877787 tracked setup for v1.1.0hd.

(In reply to John O'Duinn [:joduinn] from comment #0) > Before 09dec, we'll be needing automation support for b2g v1.3, so that v1.4 > work can start landing on master. This should read "Before 03-feb-2014...", sorry for any confusion. Fixing bug dependencies to match reality.

Let's comment out the push as well.

We can pause the whole repo sync because it's not production yet.

Comment on attachment 8363165 [details] [diff] [review] legacy vcs-sync: pause 1.3 syncing Review of attachment 8363165 [details] [diff] [review]: ----------------------------------------------------------------- okay after line removed. ::: keep_updated @@ +75,5 @@ > +refs/heads/$g18_v101_branch:refs/heads/v1.0.1 \ > +refs/heads/$g18_v110_hd_branch:refs/heads/v1.1.0hd \ > +refs/heads/$v12_branch:refs/heads/v1.2 \ > +refs/heads/$v12f_branch:refs/heads/v1.2f \ > +# +refs/heads/$v13_branch:refs/heads/v1.3 \ Can't comment out the line, as next line would be taken as new command. Must remove.

Comment on attachment 8363169 [details] [diff] [review] legacy vcs-sync: b2g28_v1_3 Review of attachment 8363169 [details] [diff] [review]: ----------------------------------------------------------------- lgtm

Comment on attachment 8363174 [details] [diff] [review] new vcs-sync: b2g28_v1_3 Review of attachment 8363174 [details] [diff] [review]: ----------------------------------------------------------------- lgtm

Comment on attachment 8363228 [details] [diff] [review] add to graphs http://hg.mozilla.org/graphs/rev/ce0f28ad9d57

Updated graphserver db + staging with Callek and jlund's help.

Hm, might have been better if I enabled b2g28_v1_3 and disabled aurora in two different sets of patches, so I could enable b2g28 early.

one more.

Comment on attachment 8364750 [details] [diff] [review] geckol10n Review of attachment 8364750 [details] [diff] [review]: ----------------------------------------------------------------- lgtm if you can correct or explain the one change ::: b2g/config/emulator/config.json @@ +16,4 @@ > "gaia": { > "l10n": { > "vcs": "hgtool", > + "root": "http://hg.mozilla.org/integration/gaia-1_3/" Shouldn't this be: "http://hg.mozilla.org/releases/gaia-l10n/v1_3/"

Comment on attachment 8363179 [details] [diff] [review] add to tbpl https://hg.mozilla.org/webtools/tbpl/rev/37c4ea49fd61 since we need this live by Monday.

Comment on attachment 8363179 [details] [diff] [review] add to tbpl In production :-)

Comment on attachment 8368150 [details] [diff] [review] buildbotcustom.diff Review of attachment 8368150 [details] [diff] [review]: ----------------------------------------------------------------- oh yeah - this one!

Comment on attachment 8368150 [details] [diff] [review] buildbotcustom.diff https://hg.mozilla.org/build/buildbotcustom/rev/93de57233f22

Comment on attachment 8368151 [details] [diff] [review] repo-sync-configs Review of attachment 8368151 [details] [diff] [review]: ----------------------------------------------------------------- huh - not sure how we lost that, but it belongs there.

Comment on attachment 8368151 [details] [diff] [review] repo-sync-configs http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/a326ae66029b

Comment on attachment 8363908 [details] [diff] [review] tools.diff http://hg.mozilla.org/build/tools/rev/4bf4c55aeed9

Comment on attachment 8364007 [details] [diff] [review] buildbot-configs Landed without removing aurora: https://hg.mozilla.org/build/buildbot-configs/rev/6950eb40ae3e Adding another patch to remove aurora.

Reconfiged, which should bring b2g28_v1_3 live in buildbot.

Comment on attachment 8364750 [details] [diff] [review] geckol10n http://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/53b9243d7b9f

Well, I have a patch for gecko.git (non-legacy) and a patch for mozharness configs, but I don't have a patch for beagle. Here it is.

The remove aurora portion of the configs. Carrying forward review. I'm leaving aurora in the b2g_config.py loops, since we'll need those entries when 32 merges into aurora anyway.

Comment on attachment 8368228 [details] [diff] [review] beagle http://hg.mozilla.org/build/mozharness/rev/98c4d0a88fe0 Also, fixed the emulator config.json like :hwine said in the first place. http://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/13c5c4a9103d

Comment on attachment 8364007 [details] [diff] [review] buildbot-configs With requisite followup fix: https://hg.mozilla.org/build/buildbot-configs/rev/9677e8e4ec15

Comment on attachment 8363228 [details] [diff] [review] add to graphs The graphs sql is lying to us. The branch names in the database are in the format of Mozilla-B2g26-v1.2 while the file has names in the format of Mozilla-B2g26_v1.2 (see dash/underscore difference). I'm going to patch this file to reflect reality after filing an IT bug to update the Mozilla-B2g28_v1.3 branch in the db to Mozilla-B2g28-v1.3

Since this is what's in the production db: | 171 | Mozilla-B2g18 | | 213 | Mozilla-B2g18-Non-PGO | | 199 | Mozilla-B2g18-v1.1.0hd | | 215 | Mozilla-B2g18-v1.1.0hd-Non-PGO | | 189 | Mozilla-B2g18_v1_0_0 | | 191 | Mozilla-B2g18_v1_0_1 | | 209 | Mozilla-B2g26-v1.2 | | 211 | Mozilla-B2g26-v1.2-Non-PGO | | 217 | Mozilla-B2g26-v1.2f | | 219 | Mozilla-B2g26-v1.2f-Non-PGO | | 221 | Mozilla-B2g28_v1.3 | and https://tbpl.mozilla.org/?tree=Mozilla-B2g28-v1.3&rev=53b9243d7b9f wants to insert to the Mozilla-B2g28-v1.3 branch in graphs. bug 966092 to fix the rest of this mess. graphs-- datazilla++

Comment on attachment 8368316 [details] [diff] [review] graphs2 Review of attachment 8368316 [details] [diff] [review]: ----------------------------------------------------------------- hah! I passed the eye test this time -- the '26' s/b '28', then good to go

(In reply to Hal Wine [:hwine] (use needinfo) from comment #38) > Comment on attachment 8368316 [details] [diff] [review] > graphs2 > > Review of attachment 8368316 [details] [diff] [review]: > ----------------------------------------------------------------- > > hah! I passed the eye test this time -- the '26' s/b '28', then good to go I think it's correct; I'm fixing the b2g18 and 26 as well as 28 entries.

Comment on attachment 8368316 [details] [diff] [review] graphs2 http://hg.mozilla.org/graphs/rev/4384364d175d

Comment on attachment 8368239 [details] [diff] [review] remove_aurora http://hg.mozilla.org/build/buildbot-configs/rev/782acec0572f

Comment on attachment 8363165 [details] [diff] [review] legacy vcs-sync: pause 1.3 syncing https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/49e83b3599ca

Comment on attachment 8363174 [details] [diff] [review] new vcs-sync: b2g28_v1_3 Landed on my vcs-mapper branch: https://github.com/escapewindow/mozharness/commit/d7c3afb4669dcb37e4086b4e6237ae49c3b0d74f

Comment on attachment 8363907 [details] [diff] [review] mozharness.diff https://hg.mozilla.org/build/mozharness/rev/c2740b0b6702

Comment on attachment 8363169 [details] [diff] [review] legacy vcs-sync: b2g28_v1_3 https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/0d44d88accb8

Followup fix. Yay for patches that get written+reviewed (and fixed and re-reviewed, repeat) and then need manual fixing due to conflicts! https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/a30644c7e8a9

I think we're done here.

in production