[tei-council] Release guidelines

Peter Stadler stadler at edirom.de
Tue Dec 10 09:20:32 EST 2013


Am 06.12.2013 um 18:42 schrieb Martin Holmes <mholmes at UVIC.CA>:

>>> Ah, I see what you mean -- that is bad. We need to add a step to the
>>> release process which corrects the schema pointer to point to the one in
>>> the release package itself. I would definitely want to keep the
>>> lastSuccessfulBuild pointer in trunk, though; since it's now quite
>>> complicated to build the Guidelines yourself, it's important that people
>>> working on the code can validate against the latest version of the schema.
>> 
>> Yes, sure - that’s why I was thinking to do that change in a separate branch and *not* to change this (even temporarily) in trunk.
> 
> The simplest thing would be to change it at tag time; we could script 
> that very easily.
How would you do this?
I can imagine doing this for the zip archive but how to apply this for the subversion tag?

> We should also fix the existing tags on the TEI site, I think.
Which tags? The Subversion tags?  (sorry, I’m new …)

Best
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/20131210/1df95084/attachment.bin 


More information about the tei-council mailing list