Re: Future Test Suite release process

On Jun 26, 2013, at 10:23 AM, Gavin Carothers <gavin@carothers.name> 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.

+1; I didn't see a point in removing the Turtle tests from HG; they can probably be resurrected through a reverse merge in HG.

Gregg

> Cheers,
> Gavin