W3C home > Mailing lists > Public > public-qa-dev@w3.org > April 2005

howto do punctual updates to the production validator

From: Olivier Thereaux <ot@w3.org>
Date: Fri, 29 Apr 2005 09:34:51 +0900
To: Dominique HazaŽl-Massieux <dom@w3.org>
Cc: public-qa-dev@w3.org
Message-ID: <20050429003451.GA13729@w3.mag.keio.ac.jp>

On Thu, Apr 28, 2005, Dominique HazaŽl-Massieux wrote:
> I have not updated the code running in the production validator, since
> I'm not quite sure how the validators maintainer deal with this.

The general process is to cvs commit your file, cvs tag (with -F if
overwriting a tag, but I reckon some may find that bad practice), and
cvs update -r on the production side... and be extra careful!

Things are, however, a little more complicated than that, because:
- currently the production validator lives in a particular CVS branch,
  not HEAD. You'd have to port it there (cvs get the branch, and then
cvs commit, cvs tag...)
- For the tips (and most config files), we have trashed the old config
  syntax that was confusing everyone with something sane. That means the
  port should not just be a copy.

see http://dev.w3.org/cvsweb/validator/htdocs/config/tips.cfg
e.g the difference between 1.12 (HEAD) and 1.3.2.14 (0_6 branch)

-- 
olivier
Received on Friday, 29 April 2005 00:34:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 August 2010 18:12:45 GMT