Closed Bug 481376 Opened 16 years ago Closed 16 years ago

Create Hg repository for Litmus

Categories

(Webtools Graveyard :: Litmus, defect, P2)

All
Other
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: wenzel, Assigned: coop)

References

()

Details

The Litmus project is getting some Webdev love lately and its code is still managed in CVS, which webdev does not use. Can we move it to SVN or hg, including its revision history? If SVN or hg does not really matter. My personal preference is hg, but a lot of webdev work is in SVN. So you should probably choose the one you find easier to convert to. Thanks.
coop and zach should be involved here... really, all you need IT to do is create the repo (either svn or hg). The actual conversion process doesn't require IT at all.
Group: infra
I can handle a CVS->hg conversion once a repo is setup. Not too familiar with svn, but I assume there are docs for cvs2svn if we go that route.
Punt back over when you pick your VCS.
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
Component: Release Engineering → Litmus
Product: mozilla.org → Webtools
QA Contact: release → litmus
Use hg.
Assignee: nobody → server-ops
Component: Litmus → Server Operations
Product: Webtools → mozilla.org
QA Contact: litmus → mrz
going with hg.mozilla.org/webtools/litmus/.
Assignee: server-ops → reed
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Summary: Move Litmus code from CVS to SVN or hg → Create Hg repository for Litmus
Assignee: reed → nobody
Status: RESOLVED → REOPENED
Component: Server Operations → Litmus
Product: mozilla.org → Webtools
QA Contact: mrz → litmus
Resolution: FIXED → ---
Coop, can you do this when you find time (per comment 2)?
Assignee: nobody → ccooper
Status: REOPENED → ASSIGNED
Can someone from IT help us with this?
ok, from comment#5, looks like we're going to use hg, not svn. Frederic: do you really need history, or would just the tip be ok? When we migrated Firefox, we did this, because it greatly simplifies the importing, and we left the cvs repo around if anyone cared to look at ancient history with old tags, branches, etc...
(In reply to comment #9) > Frederic: do you really need history, or would just the tip be ok? No, I don't personally need the history. It should just not be lost. So if the old repo stays where it is, I am fine with it. I just thought we should not wipe out the entire project history in the process. So just importing the latest revision would work. Thanks.
Priority: -- → P2
Repo is populated now, with history. There was apparently a mod_perl branch that Zach created ages ago that I squashed as well. You'll want to update the production install to use hg at some point. Make sure you're mindful to preserve any local changes, scripts/ and localconfig being the examples that leap to mind.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → FIXED
Oh, and for the curious, to do the conversion, I simply ran "hg convert -A usermap litmus" with the following usermap: ccooper%deadsquid.com = Chris Cooper <ccooper@deadsquid.com> ctalbert%mozilla.com = Clint Talbert <ctalbert@mozilla.com> timeless%mozdez.org = timeless <timeless@bemail.org> zach%zachlipton.com = Zach Lipton <zach@zachlipton.com>
Coop; thanks doing that, and also for the useful extra details!
err. i hope i was mozdev not mozdez and which side is the side in the repo? because i'm trying to be timeless@mozdev.org in hg consistently.
(In reply to comment #14) > err. i hope i was mozdev not mozdez > > and which side is the side in the repo? because i'm trying to be > timeless@mozdev.org in hg consistently. The typo in the usermap actually helped us here. You are still timeless@mozdev.org in hg for litmus.
That's unlikely.
Production site is still running the code from CVS. No one has re-pulled from hg AFAIK. The daily cron job to update the testcase_files/ will also need to change to hg.
Shall I create a new bug? Is it part of IT?
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.