[tei-council] Release guidelines
Martin Holmes
mholmes at uvic.ca
Wed Dec 11 08:41:54 EST 2013
On 13-12-11 01:13 AM, Peter Stadler wrote:
>
> Am 10.12.2013 um 17:45 schrieb Martin Holmes <mholmes at UVIC.CA>:
>
>> I was thinking we would make the change in the tag after creating
>> the tag. Of course, this would actually make it a branch, but
>> that's just terminology, really; in Subversion there's no
>> difference between a branch and a tag, except that you're not
>> really supposed to commit changes to a tag.
>
> Ah, I see. I didn’t expect such an abuse of standards from the TEI
> council but well, the end justifies the means … <grin/>
Indeed. Shame on us. We'll have to start calling them branches, I guess.
>
>>>> We should also fix the existing tags on the TEI site, I think.
>>> Which tags? The Subversion tags? (sorry, I’m new …)
>>
>> I was thinking of all the previous versions in the Vault:
>>
>> <http://www.tei-c.org/Guidelines/P5/#previous>
>>
>> Those files are (IIRC) on the TEI server in Virginia, and I don't
>> have a working login for that server, but I think James and
>> Sebastian do; perhaps one of them could change those xml-model
>> pointers to:
>>
>> <http://www.tei-c.org/Vault/P5/2.5.0/xml/tei/odd/p5.nvdl>
>
> Thanks for the clarification. I have to admit I actually never(?)
> use(d) the Vault. So, this is a simple copy of the Sourceforge
> repository which is created by hand by the webmaster? (the process is
> not mentioned in the build instructions at
> http://www.tei-c.org/Activities/Council/Working/tcw22.xml …)
I think this happens as part of step 7, due to the magic of the
tei-install.sh script.
Cheers,
Martin
More information about the tei-council
mailing list