[tei-council] Release Process

[Sebastian Rahtz]

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.

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