Closed Bug 508283 Opened 15 years ago Closed 15 years ago

please clone mozilla-central and l10n-central repositories to releases/mozilla-1.9.2 and releases/l10n-mozilla-1.9.2

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: aravind)

References

Details

...but not yet.

I'm filing this bug as a heads up, I'll ping / update the bug when we actually want to do it.
Ben, no point in having these bugs sitting in our queue if they are not ready to be worked on.  Please move it back once you are ready for this.
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering: Future
QA Contact: mrz → release
We're ready to clone these at any time. If you can make them read-only for now that would be great. If not, no big deal. To be clear, we want the following cloned:
mozilla-central -> releases/mozilla-1.9.2
l10n-central/* releases/l10n-mozilla-1.9.2*

This is the same we did for the mozilla-1.9.1 branch, fwiw.
Assignee: nobody → server-ops
Component: Release Engineering: Future → Server Operations
QA Contact: release → mrz
Done with the mozilla-central clone, working on the l10n thingies now.
Assignee: server-ops → aravind
Is there a well known branch point in the 1.9.1 repos?
oops, I meant the central repos.
(In reply to comment #4)
> Is there a well known branch point in the central repos?

If it's important, I'll create a tag when I do the final sync up on the day we officially branch - does it matter though?
I'd rather have them, yes. If nothing else, it will make documenting the work of migration from 1.9.2 onwards easier if the there's something consistent across locales to refer to as branch tag.
All done here from my side.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.