[tei-council] how to release errata, versions etc

Lou Burnard lou.burnard at oucs.ox.ac.uk
Tue Nov 6 08:45:21 EST 2007


I am not sure that the effort of distinguishing "text correction and 
translation fixes" from "Birnbaum-compliant schema changes" is going to 
be easy. Deciding what goes into 1.0.1 as opposed to the 1.1 fork may be 
so non-trivial as to call into question the usefulness of the distinction.

For example: changing the text describing an existing valItem is clearly 
a 1.0.1 item. Is adding a new valItem to an open list? again, presumably 
yes. But adding one to an existing closed list? clearly not. So how 
about adding the new item and changing the list from closed to open? 
Which is that?

And how about changing the text of an existing valItem/desc by inserting 
the word "not" at some strategic point?

If there is a general consensus that the distinction is useful and that 
people of good spirit will always come to the same conclusion 99.9% of 
the time when making it, I have no problem with Sebastian's proposal. I 
am just uncertain. No doubt we will develop ad hoc rules as we go along...

Sebastian Rahtz wrote:
> One thing we can discuss now is how and when to make
> a text-correction release. We will, obviously, have typos reported
> to us over the next month or two; and I will certainly have
> more translations to go in (more Japanese and Italian
> came today).
> 
> However, we should probably be much more circumspect
> about schema changes (even Birnbaum-compliant ones),
> such as adding the @who attribute to <quote> which Zamir
> asked for.
> 
> How about this for a plan:
> 
>   a) we start a new branch of the source, preparing for release 1.1.
>       this will contain schema extensions and fixes. release date
>       undefined.
> 
>    b) we commit text-correction and translation fixes to the main
>       trunk now, and prepare to release that as 1.0.1 at the same time
>       as we produce PDF (ie roughly 1st January 2008).
> 
> I am proposing that we start thinking about this as "P5 release 1.0",
> "P5 release 1.0.1" etc. so "P5" is the name of the deliverable, not
> the version number.
> 



More information about the tei-council mailing list