[tei-council] Stylesheets release, and how to make releases on new server

[Peter Stadler]

Going through the release process „What you will need before you start“ [1] as Martin suggested and wondered about 7.
First, there is something missing (or too much): "download a copy of the public key at ??? from tei-c.org:/home/tei/.ssh/id_dsa.pub“
Second, am I right that I first need access to the server and then scp the file to my machine? Or is it accessible via (anonymous) http? It sounds a little bit like that … ("download a copy“)

BTW, who is to edit the file tcw22.xml?

Peter


Am 09.01.2014 um 14:42 schrieb Martin Holmes <mholmes at UVIC.CA>:

> We should definitely document this ahead of time in TCW22 so Peter is 
> actually testing it when he does the release. Sebastian, can you confirm 
> that these steps are what you need to do?
> 
>>>     * ssh tei at www.tei-c.org
>>>     * cd private/P5
>>>     * svn up
>>>     * Utilities/tei-install.sh —package=TEIP5 —version=x.x.0
> 
> Also, do we know whether Peter will be logging in as tei, or whether 
> he'll need to get an account for himself set up by David?
> 
> Peter, if you haven't done so already, I'd go through the early part of 
> TCW22:
> 
> <http://www.tei-c.org/Activities/Council/Working/tcw22.xml#beforeStarting>
> 
> to make sure you've got yourself set up and ready (including the SSH key 
> for SourceForge).
> 
> Cheers,
> Martin
> 
> 
> On 14-01-09 03:14 AM, James Cummings wrote:
>> 
>> Should we be editing the release documentation (tcw22) to reflect
>> this in advance?
>> http://www.tei-c.org/Activities/Council/Working/tcw22.xml Or only
>> do so after the release with all the other changes?  (I suspect
>> the former...)
>> 
>> -james
>> 
>> On 05/01/14 17:51, Sebastian Rahtz wrote:
>>> I just went through the process of making a Stylesheets release, in order to fix a high profile bug
>>> reported on Saturday (if you used the @prefix on schemaSpec and made a DTD, it was a mess).
>>> 
>>> i mention this ‘cos:
>>> 
>>>    a) it demonstrates that the install script seems to run fine so far on the new TEI web server[1]
>>>    b) I really don’t want to change stylesheets again before the P5 release in a week or two unless its really essential
>>> 
>>> so if there were or are things that people are working on for their open tickets which
>>> will need changes to the ODD processing, can they flag them up ASAP?
>>> 
>>> [1] however, the setup is not what we document. I just made a copy of the
>>> script and ran it in /tmp, but that’s not very sustainable. So I have checked out
>>> P5 in ~tei/private/P5, which means that what the release technician will do is:
>>> 
>>>     * ssh tei at www.tei-c.org
>>>     * cd private/P5
>>>     * svn up
>>>     * Utilities/tei-install.sh —package=TEIP5 —version=2.6.0   # vel sim
>>> 
>>> the install of TEIP5 is untested as yet, of course, as is the step of rebuilding the
>>> eXist database for Roma.
>>> --
>>> Sebastian Rahtz
>>> Director (Research) of Academic IT
>>> University of Oxford IT Services
>>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>> 
>> 
>> 
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20140109/945df008/attachment.bin