[tei-council] 2.4.1 or 2.5.0?

[Hugh Cayless]

Since this is actually an oversight being corrected (and a useful and important change), I'd be in favor of breaking release discipline and fixing it now. As release manager, Sebastian should have final say.

On Jul 24, 2013, at 9:39 , Gabriel Bodard <gabriel.bodard at kcl.ac.uk> wrote:

> I think if we do 2.4.1 this week (as it now seems), then 2.5.0 should 
> wait until the next cycle, probably at the end of the year--when we'll 
> have a bunch of new interesting things to include, as well as just 
> correcting the oversight in `<precision>`.
> 
> There's still stuff to talk about re responsibility, relation and match, 
> for example.
> 
> G
> 
> On 2013-07-24 13:40, Syd Bauman wrote:
>> Well, this is a moot point as we're now frozen and it's not in. But
>> FWIW, I think both GB and LB are right, so I'm in favor of
>> a) adding att.ranging to <precision>, and
>> b) not doing so now, so we can make sure the examples and discussion
>>    make sense, and consider deprecating @degree
>> 
>> We can make a 2.5.0 release in a week or two, eh?
>> 
> 
> -- 
> Dr Gabriel BODARD
> Researcher in Digital Epigraphy
> 
> Digital Humanities
> King's College London
> Boris Karloff Building
> 26-29 Drury Lane
> London WC2B 5RL
> 
> T: +44 (0)20 7848 1388
> E: gabriel.bodard at kcl.ac.uk
> 
> http://www.digitalclassicist.org/
> http://www.currentepigraphy.org/
> 
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived