[tei-council] Release guidelines

James Cummings James.Cummings at it.ox.ac.uk
Fri Dec 6 08:26:30 EST 2013


On 06/12/13 10:36, Sebastian Rahtz wrote:
>> if I understand
>> http://www.tei-c.org/Activities/Council/Working/tcw22.xml
>> correctly, all the work for creating a release is done in
>> trunk. I know, never touch a running system, but wouldn’t it
>> be more elegant to have a separate release branch?
>
> i wonder whether the reason we didn’t do this was because
> no-one involved really understood Subversion branching and
> merging? I always wonder how the Jenkins CI setup would work
> if we had a branch for each release.

I think because of our existing practices we may have thought the 
pain in doing so probably didn't outweigh the benefits.

Happy to be convinced though...

-James

>
>
>
> Sebastian
>


-- 
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford


More information about the tei-council mailing list