Shouldn't each release be a fresh branch off of dev though? If the release
branch sticks around, don't we risk it diverging? That said, we could
always name them "release" and nuke that branch when we're done with it.
The Jenkins jobs will just not run if there isn't a branch with the right
name, right?
On Thu, Mar 17, 2016 at 9:06 AM, Peter Stadler
Is there any benefit in naming the release branches (both Guidelines and Stylesheets) „release-x.x.x“ rather than just „release“? If it was just „release“ we could have proper jenkins jobs for these branches [1] and wouldn’t need to update the config files for every release. (I guess we will be deleting those „release-x.x.x“ branches after the release but a „release“ branch could simply persist.)
What do you think? Peter
[1] along with documentation/archival at https://github.com/TEIC/TEI/tree/dev/Documents/Editing/Jenkins/jobs
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived