[tei-council] Release guidelines

Peter Stadler stadler at edirom.de
Fri Dec 6 10:56:31 EST 2013


> 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.

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/20131206/afcb6e7f/attachment.bin 


More information about the tei-council mailing list