- From: Guus Schreiber <guus.schreiber@vu.nl>
- Date: Thu, 27 Jun 2013 12:49:31 +0200
- To: Gavin Carothers <gavin@carothers.name>
- CC: RDF-WG WG <public-rdf-wg@w3.org>
On 26-06-13 18:23, Gavin Carothers wrote: > 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) > > Steps: > > 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. Excellent plan. I suggest to record this process on the RDF Tests wiki page. Guus > > Cheers, > Gavin >
Received on Thursday, 27 June 2013 10:49:59 UTC