W3C home > Mailing lists > Public > public-rdf-wg@w3.org > June 2013

Future Test Suite release process

From: Gavin Carothers <gavin@carothers.name>
Date: Wed, 26 Jun 2013 09:23:32 -0700
Message-ID: <CAPqY83whe_VZw91vuE3jOcpB4Y7z_DHh7_FmWgou48+o_0-5uQ@mail.gmail.com>
To: RDF-WG WG <public-rdf-wg@w3.org>
While the ship has already sailed on the Turtle Test Suite, for all of our
other test suites I'd like to make sure we end up with a process where
changes to the test suite are more visible.

Test suites are already assembled in the rdf-wg mercurial hg repository,
once we are prepared to publish it we should create a tag and simply put
the copy of the Test Suite at that tag in CVS. If there are changes to be
made to the Test Suite after that we simply make them in mercurial  and
republish with a new tag, again making a copy into CVS space. As the WG,
and general public can't see the changes tracked in CVS it doesn't work
well for transparency. (Unless of course they can in which case can someone
point to where)


1. Create Test Suite in https://dvcs.w3.org/hg/rdf/
2. Resolve to publish Test Suite
3. Tag specific revision in https://dvcs.w3.org/hg/rdf/
4. Copy tree from https://dvcs.w3.org/hg/rdf/ to
http://www.w3.org/2013/CVS space
5. Updates are made to http://www.w3.org/2013/

New publications begin at step 2 again.

Received on Wednesday, 26 June 2013 16:23:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:14 UTC