[tei-council] mess up over tei_all.xsd
bansp at o2.pl
Wed Mar 2 09:10:26 EST 2011
I'd say, in the case of a beast such as the TEI, "publish often"
whenever bugs show up, especially if you have a chance to just publish a
fix, without new features which may be in the process of being tested
against the rest of the system.
Nothing wrong with a 1.9.2 if something bad occurs after a quick 1.9.1
-- it just shows responsiveness to the community. Especially in this
case, where the problem is very local, so only those affected need to
upgrade. And as Laurent mentions -- this is to be expected right now.
It's incredible how little actually is bugged after all these
infrastructural changes --> a bow to Sebastian.
On 02.03.2011 14:31, Sebastian Rahtz wrote:
> ok, Trier says it works now, so at least thats fixed
> I'd rather not wait more than a week, if we do a 1.9.1,
> as any changes in the meanwhile by Kevin or Lou cleaning up
> old tickets will of necessity get included (since we
> operate on a single development branch, for good or bad
> - another conversation.....).
> Sebastian Rahtz
> Head of Information and Support Group, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
> Sólo le pido a Dios
> que el futuro no me sea indiferente
More information about the tei-council