Migrate SeaMonkey build system repo from CVS to Mercurial

RESOLVED WONTFIX

Status

Developer Services
Legacy VCS
RESOLVED WONTFIX
4 years ago
3 years ago

People

(Reporter: Ian Neal, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
The SeaMonkey project depends on cvs for releases (checkout patchers build system etc..) but we should move this to a mercurial which is a more modern source control application.

This is spun off from the tracking bug 1057920

Would the first step to be to create a mercurial mirror of the CVS repo?
What other steps are required? I presume a variety of people need to be involved.

Updated

4 years ago
Assignee: server-ops → nobody
Component: Server Operations → Mercurial: hg.mozilla.org
Product: mozilla.org → Developer Services
QA Contact: shyam → hwine
Actually everyone, this is WONTFIX.

We need to migrate the seamonkey build/releng repo processes from CVS to hg, yes. But we already have a repo where we'll do that:

https://hg.mozilla.org/users/Callek_gmail.com/tools
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
First step (repo creation) not needed, but still need to actually do the migration. Reopening and moving to legacy component to keep this visible. (If you want a new bug for that, fine. Please link into existing dependency chain.)
Blocks: 985022
Status: RESOLVED → REOPENED
Component: Mercurial: hg.mozilla.org → Legacy VCS
QA Contact: hwine
Resolution: WONTFIX → ---
Can you confirm migration complete, please? Thanks!
Flags: needinfo?(bugspam.Callek)

Comment 4

3 years ago
(In reply to Hal Wine [:hwine] (use needinfo) from comment #3)
> Can you confirm migration complete, please? Thanks!

Not yet, but working on it.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago3 years ago
Resolution: --- → WONTFIX
(In reply to Hal Wine [:hwine] (use needinfo) from comment #2)
> First step (repo creation) not needed, but still need to actually do the
> migration. Reopening and moving to legacy component to keep this visible.
> (If you want a new bug for that, fine. Please link into existing dependency
> chain.)

I need a bug that, when closed, means SM is clear of CVS. If you'd like a fresh bug, that's fine, but please cite it if you reclose this bug.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Comment 6

3 years ago
(In reply to Hal Wine [:hwine] (use needinfo) from comment #5)
> (In reply to Hal Wine [:hwine] (use needinfo) from comment #2)
> > First step (repo creation) not needed, but still need to actually do the
> > migration. Reopening and moving to legacy component to keep this visible.
> > (If you want a new bug for that, fine. Please link into existing dependency
> > chain.)
> 
> I need a bug that, when closed, means SM is clear of CVS. If you'd like a
> fresh bug, that's fine, but please cite it if you reclose this bug.

Ah, sorry Hal.  I'm going to close this bug and cite bug 1057920 as the
tracking bug so when that bug closes,  SeaMonkey should be off CVS.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Flags: needinfo?(bugspam.Callek)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.