W3C home > Mailing lists > Public > public-automotive@w3.org > October 2015

Update on switching to Echidna for automated publishing

From: Ted Guild <ted@w3.org>
Date: Mon, 05 Oct 2015 11:48:01 -0400
Message-ID: <1444060081.21333.27.camel@w3.org>
To: public-automotive <public-automotive@w3.org>
I have performed a number of the preliminary steps for setting up our
publications to publish automatically.  It prompted a question that I
wanted clarification on before proceeding.

https://github.com/w3c/echidna/wiki/How-to-use-Echidna-with-ReSpec-and-GitHub

A common convention is using gh-pages as the principle branch to publish
from.  Often people do away with the master branch to avoid confusion
and having to merge repeatedly.  Are the editors alright with me getting
rid of the master branch in favor of gh-pages one?

http://w3c.github.io/specs.html

https://w3c.github.io/automotive/vehicle_data/data_spec.html
https://w3c.github.io/automotive/vehicle_data/vehicle_spec.html

If people are disinclined, it would be possible but more cumbersome and
with limitations to use rawgit URIs on master branch.

Once we settle this I will make sure the gh-pages branch is current and
make various minor corrections, small validation issues, so we can start
publishing.  

https://labs.w3.org/pubrules/?url=https%3A%2F%2Flabs.w3.org%
2Fspec-generator%2F%3Ftype%3Drespec%26url%3Dhttps%3A%2F%2Fw3c.github.io%
2Fautomotive%2Fvehicle_data%2Fdata_spec.html%3FspecStatus%3DWD%
3BshortName%
3Dvehicle-data&profile=WD&validation=simple-validation&noRecTrack=false&informativeOnly=false&echidnaReady=false&patentPolicy=pp2004&processDocument=2015

After I will also setup Travis so we can create the commit hook.

https://github.com/w3c/echidna/wiki/Setting-up-Echidna-as-a-GitHub-hook

-- 
Ted Guild <ted@w3.org>
W3C Systems Team
http://www.w3.org

Received on Monday, 5 October 2015 15:48:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 24 October 2017 18:52:44 UTC