Closed Bug 1858765 Opened 1 year ago Closed 1 year ago

comm-unified repository

Categories

(Developer Services :: Mercurial: hg.mozilla.org, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rjl, Assigned: rjl)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

In order for some of the release engineering automation to work, (specifically treescript merges from branch to branch), a comm-unified repository will be needed that works like mozilla-unified but contains the comm-* repos.

Specifically:

comm-central
comm-beta
comm-release *
comm-esr{FOO}

Note that comm-release should be whatever repo is the end result of bug 1858761.

If there is code to be updated that I can tackle, I am happy to do so. I thought I recalled seeing it in version-control-tools, but I may be thinking of something else...

Timeline-wise I'd like this to be ready by December 1.

We'll need to create a config file that looks like the unify-mozilla-unified.ini file and set up a repo unify process on hgmo.

Blocks: 1859877
Blocks: tb-monthly
Assignee: nobody → rob
Attachment #9358767 - Attachment description: WIP: Bug 1858765 - Config file for comm-unified repository. → Bug 1858765 - Config file for comm-unified repository.
Status: NEW → ASSIGNED
Blocks: 1864894
Blocks: 1864901
Attachment #9358767 - Attachment description: Bug 1858765 - Config file for comm-unified repository. → Bug 1858765 - Config file for comm-unified repository. r=sheehan

Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/4d2f38c5cce7
Config file for comm-unified repository. r=sheehan

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
See Also: → 1866392
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: