[tei-council] reminder

[James Cummings]

Another way to do this is to look at bugs/feature requests since last 
release.  I've been taking that approach and then looking in the 
Guidelines places I think that element/content model/etc. might be (or 
should be) mentioned. I realize this is more haphazard though, and 
hasn't been too successful at finding problems yet.

-James

Daniel Paul O'Donnell wrote:
> Lou,
> 
> Could we maybe assign ranges like we did before? I note sheepishly that 
> having said this, I can't do anything, since the TEI-Mellon RFP bids 
> have come in and I'm busy with them and setting up the final stage of 
> the competition right through July 6th.
> 
> -dan
> 
> Lou Burnard wrote:
>> Just a reminder that we'd like to get the error fixing release 1.4.1 out 
>> as soon as possible. The plan (as James said last week) is to push the 
>> button on 1 July, so you have four days left.
>>
>> As James says: If we are going to do a maintenance release anyway, could 
>> I humbly  suggest that Council members really scour the Guidelines and 
>> reference pages making sure that we find any other errata or things that 
>> we've implemented but not changed the related text about, or similar  
>> omissions? We might as well try to fix as many bugs all at once!
>>
>> A null report (i.e. "i looked at chapters x y and z and they seem fine") 
>> is perfectly acceptable!
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>   
> 


-- 
Dr James Cummings, Research Technologies Service, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk