Re: Subversion vs Mercurial for test suite repository

Le Mar 10 mai 2011 13:48, Linss, Peter a écrit :
>

Hello Peter,

Thanks for your quick reply.


> 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


I am looking at KPackageKit (main KDE software management system)
softwares under "Developer tools" category and there are a bunch of
softwares supposed to support VCS, others CVS (eg Cervisia
http://cervisia.kde.org/ ) . If only I would be sure if CVS is the same
as VCS.

CVS: Concurrent Versioning System ? Concurrent Versions System ?

VCS: Versioning Control System ? Version Control System ?

(newcomer question): Overall, what is the relationship between CVS (or
VCS) and SVN?

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


Gnome/Nautilus is for Ubuntu. I use Kubuntu. TortoiseHG is not in the
list of development softwares for KDE anyway.


Right now, when I list all possible Version Control softwares for KDE, I
get a list of 10:

Bazaar Explorer
Bazaar Version Control System
Cervisia
Cola Git GUI
Giggle
gitg
gquilt patch manager
KDESVN (which I have used and use so far)
qgit
tkcvs

and none of them are listed at
http://mercurial.selenic.com/wiki/OtherTools

unless gquilt == gquilt patch manager


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


Yes that would help.


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

One question here.

If
/source/approved/css2.1/src
has 8000 testcases, then I will have to have a (mirror) local copy
(downloaded onto my system) of those 8000 testcases with the same
directory structure, right? correct?


> 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


I have been working on all my testcases today. I have now 50 or so. I
just forgot I had already a bunch waiting in my /incoming folder.

I'll prioritize working on these from now on.

best regards, Gérard
-- 
Contributions to the CSS 2.1 test suite:
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/

CSS 2.1 Test suite RC6, March 23rd 2011
http://test.csswg.org/suites/css2.1/20110323/html4/toc.html

CSS 2.1 test suite contributors:
http://test.csswg.org/source/contributors/

Received on Tuesday, 10 May 2011 22:33:41 UTC