1120719 - Migrate SeaMonkey build system repo from CVS to Mercurial

Status: RESOLVED WONTFIX

(Developer Services :: Legacy VCS, defect)

Description

[Ian Neal]

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.

Comment 1

[Justin Wood (:Callek)]

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

Comment 2

[Hal Wine [:hwine] use NI!]

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.)

Comment 3

[Hal Wine [:hwine] use NI!]

Can you confirm migration complete, please? Thanks!

Comment 4

[Edmund Wong (:ewong)]

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

Not yet, but working on it.

Comment 5

[Hal Wine [:hwine] use NI!]

(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.

Comment 6

[Edmund Wong (:ewong)]

(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.