[tei-council] release process

[Peter Stadler]

Dear all,

during the release process of 2.6.0 we had to roll back to release 2.5.0 at some stage because we found some broken links in the HTML version of the Guidelines. Call me conservative, but I think it might be a good idea to 
1. upload the new Guidelines to tei-c.org
2. Check the release
3. AND THEN symlink ‚current‘ to point at the new release

We could insert a simple ‚read -p‘ after line 60 in tei-install.sh or even split the script in two (three)
* upload2tei-c
* make-current
* upload2sf

Comments?
Peter


-------------- 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/20140123/3254d6e6/attachment-0001.bin