[tei-council] Release guidelines

Sebastian Rahtz sebastian.rahtz at it.ox.ac.uk
Fri Dec 6 05:36:20 EST 2013


On 6 Dec 2013, at 09:03, Peter Stadler <stadler at EDIROM.DE> 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.



Sebastian


More information about the tei-council mailing list