[tei-council] Release guidelines

[Martin Holmes]

On 13-12-12 04:30 AM, Sebastian Rahtz wrote:
>
> On 12 Dec 2013, at 00:18, Martin Holmes <mholmes at uvic.ca> wrote:
>>
>> I don't think it is, actually. People working in the SVN Source need to be validating against the latest schemas (which since so few of us can build locally now, are on Jenkins).
>
> that I understand
>
>> People working with Spec files from a distributed package need to be validating against the schema that was distributed with those Spec files. In both situations, confusing invalidities will arise pretty quickly if they're pointing at the wrong schema.
>
> I wonder if anyone has _ever_ looked at the Spec files from a distributed package? unless we have computer archaeologists
> amongst us.

I'm no archeologist, but I often do this. When I'm contemplating a 
customization, I usually want to look at the content model and the 
attribute membership of the element. I go to the Spec files to do that. 
I suppose I should look at the element's documentation page, but I'm 
used to looking at the Spec files.

Cheers,
Martin

>
> anyway, fix now in place. the P5 Build will now change the source XML files to point to the copy of p5.nvdl local to them,
> at the point the distribution is created
>
> you’ll see the effect when the current build has finished.
>
> current release on web site changed in situ
> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>