[tei-council] Next TEI-C Guidelines Release (presumably 2.6.0)

[Martin Holmes]

On 14-01-07 12:22 PM, Sebastian Rahtz wrote:
>
> On 7 Jan 2014, at 20:04, Martin Holmes <mholmes at uvic.ca> wrote:
>
>>
>> True indeed. But the more I think about it, the more I rather like the
>> idea that the Jenkins log parser file might be a locus for managing our
>> deprecation warnings. It's in SVN so anyone could edit it, and could add
>> a preliminary step to all the P5 builds that just exported the latest
>> version into /var/lib/jenkins before building.
>
> it’s not that simple, as the config needs to be installed on the Jenkins server,
> which is a rather specialised job

I must be misunderstanding something, then. The unstable build arises 
out of WARNINGs which show up in the console output during a build. 
There are large numbers of errors and warnings during that process, but 
we "suppress" most of them using the hudson-log-parse-rules file here:

<https://sourceforge.net/p/tei/code/HEAD/tree/trunk/Documents/Editing/Jenkins/hudson-log-parse-rules>

If someone were to add regexes to that file for each of the warnings 
arising out of deprecation, which look like this:

<WARNING>Schematron warning:
WARNING: use of deprecated element — The TEI-C may drop support for the 
relationGrp element as early as 2014-06-17.
[Test: true()] Location: 
/TEI[1]/text[1]/body[1]/div[13]/div[3]/div[4]/div[4]/specGrp[1]/elementSpec[22]/exemplum[1]/egXML[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]/relationGrp[namespace-uri()='http://www.tei-c.org/ns/Examples'][1]</WARNING>

or like this:

[xslt] WARNING: use of deprecated attribute — The TEI-C may drop support 
for @type of the biblScope element as early as 2014-12-17.

We could add a global trap for "use of deprecated element", and then the 
Jinks build would no longer be unstable. We could also add specific 
regexes for each deprecated construct error.

Anyone could add or remove these regexes from the file at any time. 
Then, if we made the first step in each P5 build to check out this 
export this file from SVN to /var/lib/jenkins (which would be fine, 
because the build runs as the jenkins user and the file is owned by that 
user), then the build would not be unstable.

If we then periodically looked at those regexes and deleted any obsolete 
ones, everything would work fine, wouldn't it?

Cheers,
Martin

>
> i would go back to the simplest method, which is remove examples
> from deprecated elements…..
> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>