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

[Christian Wittern]

Sebastian Rahtz wrote:
> Christian Wittern wrote:
>> I am not so sure the branching is a useful approach.  Do we envision 
>> releasing further maintenance releases of the stable 1.0x branch 
>> beyond Jan2008?  Once we produced the PDF (and book?!), this surely 
>> does not make a lot of sense.
> I find myself out on a limb here. It seems obvious to me that
>
>  a) we should not just update the live version, but should make formal 
> releases
>  b) we should distinguish wordsmithing changes fron substantive changes
>
Well, I do not disagree to this.  It all depends on many things, for 
example, how frequently we want to release.  If we have, say, a release 
once per year that would mean there would be both changes to the wording 
and schematic changes.  Frankly, I am not sure if we should release more 
frequently.  Most users will get a working schema when they start a 
project and most likely not update thereafter.  At least that is the way 
I see projects working.  

>>   On the other hand, if we are just talking about 2-3 months, it is 
>> not really worth the trouble.  In the long run, it will be difficult 
>> to keep track of two different branches, me thinks.
> thats why we have Subversion. its the way its supposed to work.....
>
I know.  But nevertheless, I find myself looking at different files and 
getting confused....

Christian

-- 

 Christian Wittern 
 Institute for Research in Humanities, Kyoto University
 47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN