W3C home > Mailing lists > Public > public-css-testsuite@w3.org > May 2011

Re: Subversion vs Mercurial for test suite repository

From: Linss, Peter <peter.linss@hp.com>
Date: Tue, 10 May 2011 20:48:53 +0000
To: "css21testsuite@gtalbot.org" <css21testsuite@gtalbot.org>
CC: "public-css-testsuite@w3.org mailing list" <public-css-testsuite@w3.org>, CSS WG <w3c-css-wg@w3.org>
Message-ID: <6DC035B9-B18C-4066-B6F2-4CF8E21931AC@hp.com>

On May 10, 2011, at 10:26 AM, Gérard Talbot wrote:

> 1- I used to use KDESVN to make changes to existing tests and to submit
> new tests. What will I be supposed to use then when Mercurial is going
> to be in effect, implemented? I need something that will work under
> Linux KDE.

I knew the developers wouldn't balk at Mercurial (much), but people like you are my main concern. We haven't made the decision to switch yet (but I'm certainly leaning that way). Your feedback to this decision is very important.

There seems to some some degree of work under way to add Mercurial support to Dolphin, but it's apparently not there just yet. See:
https://bugs.kde.org/show_bug.cgi?id=164732

There are a bunch of GUI tools that work with Mercurial, please take a look and see if any of them meet your needs. There are also several editor environments that integrate with it.

See:
http://mercurial.selenic.com/wiki/OtherTools

TortoiseHg has Gnome/Nautilus support, I don't know if that can work for you...

Perhaps someone with more experience with Mercurial and KDE can chime in here?

Another way to go here is to enable WebDAV support for the repository (which is something I was planning on doing at some point anyway). That way you should be able to access the repository just like a regular file system.

> 
> 2- I have been waiting to submit new testcases (at least 17 entirely
> new, about 20 to modify) for many months now because of the test suite
> freeze. I wanted to submit those testcases this week or this weekend. Is
> it already too late now?

As Elika said, you should be good to go there. 

One thing, if you're making changes to your existing tests that have already been moved into approved/css2.1/src, please svn copy the files back into your submitted folder and then submit the changes there. That's going to be the workflow going forward for modifying approved tests and I'll soon be adding access control to the repository to enforce that policy, so best to start now.

Peter
Received on Tuesday, 10 May 2011 20:49:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 May 2011 20:49:59 GMT