[tei-council] New document describing release steps

Martin Holmes mholmes at uvic.ca
Mon Feb 6 11:41:14 EST 2012


Hi there,

It just occurred to me that the script could curl P5/VERSION from the SF 
repo to get the version info, couldn't it?

Cheers,
Martin

On 12-02-06 01:14 AM, Sebastian Rahtz wrote:
>
> On 6 Feb 2012, at 02:17, stuart yeates wrote:
>
>> Could the line:
>>
>> ./tei-install.sh --package=TEIP5 --version=X.X.X --sfuser=username
>>
>> not be simplified by having the script look in P5/VERSION for the
>> version number? Then it'd be one less thing with a chance to go wrong /
>> out of sync.
> No, because the script is not running with a copy of P5 in front of it. It uses the --version
> to know which file to grab from the Jenkins server which has prepared the release.
> The script itself does no building, it just pulls zip files and unpacks them
> in the right place.
>
> --
> Stormageddon Rahtz
> Head of Information and Support Group, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> Sólo le pido a Dios
> que el futuro no me sea indiferente
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)


More information about the tei-council mailing list