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

Subversion vs Mercurial for test suite repository

From: Linss, Peter <peter.linss@hp.com>
Date: Mon, 9 May 2011 18:48:39 -0700
Message-Id: <4D80612A-9CD1-4B5B-A204-B7478983ED4D@hp.com>
Cc: CSS WG <w3c-css-wg@w3.org>
To: "public-css-testsuite@w3.org mailing list" <public-css-testsuite@w3.org>
I'm beginning work on a management system for our test suite repository (it's called Shepherd).

The management system is going to be tightly coupled to the version control system, which is currently Subversion.

The issue here is that W3C has an interest group currently focused on building test suite tools for use by all the working groups. It looks like our harness, build system and Shepherd are likely going to serve as the foundation for the W3C wide set of tools. That IG however, has decided to use Mercurial for their test suite repository.

This means that we either switch our repository over to Mercurial, we keep on with a diverging set of testing tools, or I try to build the tools to run on both Subversion and Mercurial (which I'd rather not do). 

I think, in the long run, we'd be better served to keep our tools and testing infrastructure aligned with the rest of W3C. This means us switching to Mercurial. And if we're going to do it, the sooner the better.

Before I pull the switch and change our repository over, I wanted to get some feedback, so, thoughts?

Received on Tuesday, 10 May 2011 01:49:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:23 UTC