572789 - please start indexing http://hg.mozilla.org/releases/mozilla2.0 on mxr

Status: RESOLVED FIXED

(Webtools Graveyard :: MXR, defect)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

At present there is not an l10n branch for this branch.

Comment 1

[timeless]

So...

[ -d /data/mxr-data/mozilla1.9.3/mozilla ] && rmdir /data/mxr-data/mozilla1.9.3/mozilla 2>&1; cd /data/mxr-data/mozilla-central/mozilla-central;time  (hg  clone  .#GECKO_1_9_3_BASE /data/mxr-data/mozilla1.9.3/mozilla || hg  clone  . /data/mxr-data/mozilla1.9.3/mozilla) 2>&1;cd /data/mxr-data/mozilla1.9.3/mozilla;perl -pi -e 's!default =.*!default = http://hg.mozilla.org/releases/mozilla-1.9.3!' .hg/hgrc;time  hg  up  2>&1;abort: unknown revision 'GECKO_1_9_3_BASE'!

Pike told me:
"it's a throw-away branch for now. 
right now, it's just set up to bring the infra to speed"

but w/o that tag, i'm not sure what mxr should do. it's likely to get terribly confused (if you actually use a different branch point later).

http://mxr-test.konigsberg.mozilla.org/mozilla1.9.3/source/ exists now and is tracking this stuff (it isn't cron'd, but the fallback code did pick hg 1.9.3 so if there was a cron, it would update properly). And l10n-mozilla1.9.3 is also present on konigsberg.

* I could push this changeset and then you can only deploy the cron job to actually trigger the root for mxr. But then people would see the empty roots.

* I could provide a changeset as an attachment and then someone else could apply and push it when IT is ready.

Comment 2

[Shyam Mani [:fox2mike]]

What's the action here? What do you need IT to do?

Comment 3

[timeless]

Attachment: changes

So, this is the changeset. It should be applied to tip and pushed when we want to do so.

There are different choices for when you choose to deploy it.

If we deploy it early, then at some point, someone will probably have to file a bug against server ops asking to blow away the /data/mxr-data/mozilla1.9.3 and /data/mxr-data/l10n-mozilla1.9.3 directories.

Alternatively, we can wait until they're actually happy and tag 1.9.3 and then deploy this changeset.

Either way, after deploying the changeset, you need to add a cron bit for the tree pair.

Comment 4

[Reed Loden [:reed]]

It's "mozilla2.0" now. 1.9.3 is dead.

Comment 5

[Reed Loden [:reed]]

er, "mozilla-2.0"

Comment 6

[timeless]

http://hg.mozilla.org/webtools/mxr/rev/28285b103886