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

[Lou Burnard]

Dan O'Donnell wrote:
> Of course one should read all the way through a thread before
> responding:
> 
> I like all of this, except for 3: is there a reason not to keep the sf a
> "use at own risk bleeding edge" repository? I.e. make the fixes and park
> them during the inter-public-release period?
> 

Yes: it isn't always obvious that some proposed change is actually a 
"fix", rather than a new headache!

In general I think it makes sense to allow for a period of reflection 
and discussion before a non-trivial change is actually made.