[tei-council] oxygen-tei release

[Martin Holmes]

I guess the question is whether we want the release technician to take 
care of this (in which case a script would be great, but there would 
also be the issue of permissions to upload to Google Code), or whether 
we view it as peripheral to the main release, and hope Sebastian is 
happy to continue doing it. A middle ground would be for three or four 
of us to have the know-how and rights to do this, so it doesn't always 
have to be Sebastian.

Cheers,
Martin

On 12-02-03 07:52 AM, Sebastian Rahtz wrote:
> I have copied all the latest and greatest to http://code.google.com/p/oxygen-tei/
>
> for reference, one has to
>
>    - check out the source using Subversion
>    - copy all the xml tree  from the current release
>    - copy in an oxygen.jar from current oxygen
>    - build the zip with Ant
>    - upload the zip to googlecode
>
> scriptable, in due course, but I feel weak today.
> --
> 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)