[Tracking Bug] SeaMonkey's CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website)

RESOLVED FIXED

Status

SeaMonkey
Release Engineering
RESOLVED FIXED
3 years ago
2 years ago

People

(Reporter: ewong, Unassigned)

Tracking

({meta})

Trunk
x86
Windows Vista
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

User Story

The SeaMonkey project depends on cvs for releases (checkout patchers etc..)
and, for the website. We should move these to a modern source control application.

1) The easiest would be SVN since the commands and handling are almost identical but with benefits (repo-wide revisions, ability to rename/move without losing history)

2) Mercurial: Compared to SVN, this gives us patch queues and binary patch support. The Mozilla website people don't use Mercurial for any other website, web hosts might not have it installed.

3) git: SeaMonkey developers don't understand git. This will be "yet another tool" we need to learn, but "the whole world" is on GitHub nowadays so it's worthwhile to learn. And all Mozilla website properties are either on git or planned to move there.
(Reporter)

Description

3 years ago
The SeaMonkey project depends on cvs for releases (checkout patchers etc..)
and for the website.

We *really* should move away from cvs and to something a little more 
recent. i.e. Mercurial or git.

Since everyone's used to Mercurial, I think that's the best thing to use.
(Since it affects the website, going to loop Jens into this).
There are two large(ish) projects involved.

Releng Automation

SeaMonkey Website

The former I know what to do, just haven't had time to prioritize.

The latter Jens KaiRo and MoCo have all expressed interest in getting rid of, it just requires coordination from a few teams, due to the way the website updates. And the task has not fallen on free time/priority of any involved at the same time in order to get it done.

Comment 2

3 years ago
For one thing, let's please do two bugs here, the build system and the website are not related to each other at all.

Fore the other, I personally remain convinced that hg is the right tool for the build system stuff as that's what we're using for all build system things - for the website, I strongly feel that hg is the wrong tool as nobody uses it for web properties and it might not be installed on the web servers that are hosting the site, as everything website is being done in git at Mozilla and elsewhere.
(Reporter)

Comment 3

3 years ago
(In reply to Edmund Wong (:ewong) from comment #0)
> The SeaMonkey project depends on cvs for releases (checkout patchers etc..)
> and for the website.
> 
> We *really* should move away from cvs and to something a little more 
> recent. i.e. Mercurial or git.
> 
> Since everyone's used to Mercurial, I think that's the best thing to use.
> (Since it affects the website, going to loop Jens into this).

Err didn't I say 'loop Jens into this'?  Where's the needinfo?  *smacks head*
Flags: needinfo?(jh)
First of all, I don't have a problem with decoupling the build and website stuff; I think that's a good idea.

For the website, the easiest would be SVN since the commands and handling are almost identical but with benefits (repo-wide revisions, ability to rename/move without losing history). But that wouldn't give us patch queues and binary patch support (at least not as in provided by the RCS itself). Mercurial would be the easiest alternative for me since I have enough (user-) experience with that but zero experience with git, but if someone else took care of setup (esp. concerning automatic checkout and website updating on the server) and instructing me, git would probably work, too (no idea about up- and downsides really).
Flags: needinfo?(jh)

Updated

3 years ago
User Story: (updated)
Summary: SeaMonkey's CVS dependency really should be removed. → SeaMonkey's CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website)

Updated

3 years ago
User Story: (updated)

Updated

3 years ago
User Story: (updated)

Comment 5

3 years ago
Since there is a HgSubversion extension for Mercurial which establishes a two way bridge I think SVN is the way to go. This covers users of Mercurial and subversion which is everyone who needs to work on the website.

Comment 6

3 years ago
As long as I don't have to touch it, SVN is fine for the website. But just don't expect me to ever do anything with it again.

Updated

3 years ago
Depends on: 1120709

Updated

3 years ago
Depends on: 1120719

Updated

3 years ago
Keywords: meta

Comment 7

3 years ago
Note that Mozilla's CVS will be decommissioned in Q1, so this bug now has a deadline. Happy to help the needed work happen to migrate SM off cvs.mozilla.
(Reporter)

Updated

3 years ago
Depends on: 1121281
Blocks: 985022
(Reporter)

Updated

3 years ago
Summary: SeaMonkey's CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website) → [Tracking Bug] SeaMonkey's CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website)
As I commented in the remaining two dependencies, SeaMonkey is now late to complete their migration work. CVS will be maintained a short while longer to accommodate but will be decommissioned in the coming weeks. This work needs to be prioritized and completed to avoid impact to the SeaMonkey project.
SeaMonkey has been off for several months, afaik. closing - thanks!
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.