I would suggest doing it in such a way that major changes only effects workshops that have not yet set up there workshop website.
That is, make the change in such a way that getting it requires pulling workshop template again. Something like a git.io page for each major lesson release and the template references that instead of just the latest. This way workshops that have are already getting underway (forked the template) won't have things change under them as they will reference the major release it place when they were forked. Cheers! -Tyson On Mon, Jan 11, 2016, 11:44 sheila miguez <[email protected]> wrote: Are there plans afoot to tag releases to help prevent this pain? I wouldn't want to work on the development branch of something in production.
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
