[tei-council] Jenkins config changes

[Sebastian Rahtz]

I observe that this release's problems were
only spotted thanks to David's eagle-eyes.  We would not have been
saved by an intermediate release in any formal way, as we would have
been blind in the same way.

i think a more important rule is to have a week's freeze before a release,
and an action on everyone to check the lastSuccessfulArtefacts
in Jenkins for oddities. 

it wasn't the 2.1.0 per se which was wrong in the files, but
the wrong content.....
--
Sebastian Rahtz      
Director (Research Support) of Academic IT Services 
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431