[tei-council] Next Release; Codename: GroundHog Day

Martin Holmes mholmes at uvic.ca
Thu Feb 2 11:00:32 EST 2012


The freeze doesn't apply to fixing the error in the readme file that I 
added in step 1, of course. :-)

There will now be a short interlude while the Jinkses rebuild the broken 
documentation....

Cheers,
Martin

On 12-02-02 05:54 AM, James Cummings wrote:
> On 02/02/12 13:36, Martin Holmes wrote:
>> OK, Jenkins is updated, and the VERSION file, readme and guidelines-*
>> files have been done. Waiting for the Jinkses to do their thing. Could
>> we hold off on commits for the rest of the day, just to keep things simple?
>
> For those following along a home, this is Martin doing step 4 of:
>
> http://www.tei-c.org/Activities/Council/Working/tcw20.xml#release-steps
>
> in announcing a temporary freeze on commits to SVN to the council
> mailing list.
>
> (Because, of course, if you commit something, Jenkins fires off
> again and we have to wait through the entire build again.)
>
> -James
>
>>
>> Cheers,
>> Martin
>>
>> On 12-02-02 05:17 AM, Martin Holmes wrote:
>>> I'm up and beginning work on it now. I'm currently working with
>>> Sebastian to get my Jenkins server in sync with his, and I'm writing the
>>> release notes. Hoping to get those done, and VERSION updated, before
>>> breakfast, then during the time when I'm going to work, the Jenkins
>>> servers will do their thing and I'll have release packages ready by the
>>> time I get to the office. Then I'll carry on from there.
>>>
>>> Cheers,
>>> Martin
>>>
>>> On 12-02-02 02:14 AM, James Cummings wrote:
>>>> On 02/02/12 09:57, James Cummings wrote:
>>>>>
>>>>> I believe Becky is arguing that it should be target not type.
>>>>
>>>> And I was slower than Lou in pointing it out, and indeed fixing
>>>> it in SVN.
>>>>
>>>> On the topic of TEI Guidelines releases over the last couple days
>>>> I've updated tcw20.xml with a list of steps for a 'release
>>>> technician', who is the person in charge of making the release
>>>> (in this case Martin), with a list of steps that the technician
>>>> must ensure are completed.
>>>>
>>>> Martin, Sebastian, and I have talked through some of them which
>>>> are a bit vague at the moment (like "Ensure that the oxygen-tei
>>>> project is updated"), but if I've left out any steps do please
>>>> let me know (or add them to the list if you are able). We may
>>>> break out 'How to release the TEI Guidelines' as a separate
>>>> document from its current place in 'How to edit the TEI
>>>> Guidelines' eventually.
>>>>
>>>> As it is about 10am here that means it is about 2am in Vancouver.
>>>> When Martin wakes up (this afternoon for my timezone) he will
>>>> begin going through those steps.  *If* all goes smoothly then I
>>>> *believe* that this may be the first release of TEI P5 that has
>>>> not been pushed live by someone affiliated in some way with
>>>> Oxford. (Correct me if I'm wrong Lou?)  If that is indeed the
>>>> case I'd like to include it in the announcement to TEI-L as an
>>>> indication of how the TEI is becoming increasingly a distributed
>>>> open source project, etc.  (Not that it wasn't before but it is
>>>> good if it is seen as such.)
>>>>
>>>> -James
>>>>
>
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)


More information about the tei-council mailing list