[tei-council] Release Process

Martin Holmes mholmes at uvic.ca
Fri Jan 18 08:48:02 EST 2013


On 13-01-18 05:43 AM, Sebastian Rahtz wrote:
>
> On 18 Jan 2013, at 13:40, Martin Holmes <mholmes at uvic.ca>
>   wrote:
>>
>> Watching the release process yesterday made me think again about using
>> git. If Council members could continue their schema-changing work in
>> their own forks, leaving the trunk unchanged, during the two-week
>> release period, we might have less instability. Then immediately after
>> release, they could merge their branches and let Jinks have at them.
>>
> nice idea, but don't most people rely on Jenkins to catch
> their little mistakes of validity etc? I'd happily work away in my fork,
> but I do all my testing on the command line - others need
> J's help.

When I said "Council members", it was mainly you I was thinking of. :-) 
But most of us should be deployed typo-hunting during that period 
anyway. Enthusiastic folks can be shown how to do "make validate" on 
their local machine.

Cheers,
Martin

> --
> Sebastian Rahtz
> Director (Research Support) of Academic IT Services
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>

-- 
Martin Holmes
mholmes at uvic.ca
UVic Humanities Computing and Media Centre


More information about the tei-council mailing list