[tei-council] January TEI Release

[Kevin Hawkins]

I've just noticed that the Oxford Jenkins is outdated.

You'll notice that the citation including "Historical Social Research" 
contains biblScopes outside of imprint at

http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/CO.html

but they are still inside the imprint at

http://tei.oucs.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/CO.html#COBI

The relevant change was committed on November 3!

--Kevin

On 12/26/12 2:36 PM, Martin Holmes wrote:
> When you read the chapter of your birth month (good idea, James), it's
> best to read one of the current Jenkins build versions:
>
> <http://teijenkins.hcmc.uvic.ca/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/index-toc.html>
>
> <http://tei.oucs.ox.ac.uk/jenkins/job/TEIP5/lastSuccessfulBuild/artifact/release/doc/tei-p5-doc/en/html/index-toc.html>
>
> (one at Oxford, one at UVic, both hopefully identical) so that you're
> reading the very latest build, including any changes since the last
> release. Differences will be minor, but it is most important to proof
> the latest changes, which are only in the Jenkins builds.
>
> Cheers,
> Martin
>
> On 12-12-26 11:16 AM, James Cummings wrote:
>> Hi all,
>>
>> Hugh mentions that 17 January might be a good day for him to do a
>> TEI release and it is a day that I'm relatively free as well.
>>
>> Could I propose that we _try_ to stop any schema-affecting
>> changes to the TEI SVN repository on the evening of the 15th
>> January?  (obvious exceptions being solving bugs introduced in
>> the run up to that, typos, etc.)
>>
>> Also, some time before then, could everyone read the chapter
>> whose number is the same as the month of their birth.  (I.e. my
>> birthdate is in December, like Lou's, so we'll both read chapter
>> 12).
>>
>> I'm not in any way thinking this will get us a good complete
>> coverage, but at least means some spot proofreading will be done
>> and means we don't need to come up with a set list of
>> assignments, etc.  Obviously any typos, lack of clarity, etc. can
>> just be corrected. Anything you think warrants a ticket, should
>> be created.
>>
>> I've assigned the open SF bugs without ticket owners (only a
>> handful) and will be doing so with the SF feature requests soon.
>>
>> -James
>>
>