[tei-council] New document describing release steps

[James Cummings]

That sounds like a volunteer to me!

Barring major or urgent bugs and such, I had mentally timetabled 
that a release should happen awhile after our April meeting. End 
of June start of July?  Does that seem like a good idea? The idea 
being we would decide a lot of problematic tickets at the face 2 
face and then have a deadline about a month and a bit later to 
have completed the work arising.

It might be a bit biased of me to suggest that we aim for 1 July 
and call this release Codename: Canada Day 
http://en.wikipedia.org/wiki/Canada_Day ... It is probably not a 
good idea to tie the codename of the release (so we know which 
one we're talking about) to a specific date.

While this is a bit of fun, any suggestions on a naming strategy 
for such codenames?

-James


On 03/02/12 12:57, Gabriel Bodard wrote:
> Thanks and congratulations to Martin for carrying out this release and
> for taking pains to improve the documentation thereof.
>
> I wouldn't mind trying to out myself at some future occasion (I presume
> we're not planning to release every couple weeks from now on!). The
> rationale for this (beyond my desire for self-improvement) would be that
> I am a lot stupider and a *lot* less technically adept than Martin, so
> this would be a sterner test of the foolproofness of the documentation
> and process.
>
> G
>
> On 2012-02-03 04:42, Martin Holmes wrote:
>> Following my thrilling day of first-times (first time releasing TEI,
>> first time retweeting someone else's tweet, first time using IRC), I've
>> put together a more detailed set of instructions for future release
>> technicians:
>>
>> <http://www.tei-c.org/Activities/Council/Working/tcw22.xml>
>>
>> I've taken the core information in TCW20 relating to building a release,
>> and elaborated and extended it to include things we didn't know we
>> didn't know until today. I've also tried to explain why you take each
>> step and how it works, so you don't find yourself blindly following
>> mysterious instructions.
>>
>> Please take a look through the document. If you've done a release
>> before, check to make sure I haven't left anything out or got anything
>> wrong. If you haven't done one, read it and see if you think it would be
>> clear and detailed enough to help you through the process.
>>
>> I haven't made any changes to TWC20, but if the new document is
>> acceptable, I propose removing all those bits from TCW20 and replacing
>> them with a reference to the new doc. I haven't published the new doc
>> yet, so it doesn't appear on the TEI site menu.
>>
>> I shall close with the now-traditional expression of hatred for the CMS
>> system, which I must utter every time I have to interact with it. GRRR. ;-)
>>
>> Cheers,
>> Martin
>


-- 
Dr James Cummings, InfoDev,
Computing Services, University of Oxford