Freeze obviously did not actually happen today (Tue 03-15). Luckily, we built a week of extra time into the schedule, so this doesn't bother me. Elisa and I spoke on the phone today, and hope that the various loose ends will be tied up by tomorrow late afternoon or early evening our time for the actual freeze. Question for everyone: are we still releasing on SourceForge as well? Hugh -- Looks fine to me. Question, though: why do we bother with a separate release branch, rather than use 'master' for this purpose? (I'm not suggesting we should use master, I just don't see why not.) As for the Stylesheets, I'm more than happy either way -- but I think that whatever we do for the Stylesheets should, as far as possible, mirror the process that we do in P5/ ... i.e., make the same branches, have same review period during which only bug-fixes should get checked into new branch, etc.
Suggested changes to TCW22 ( http://www.tei-c.org/Activities/Council/Working/tcw22.xml):
"At least one week before releasing, we enter a review period, during which the only changes made to the code to be released should be to fix errors, rather than to add new features. A release branch will be created by the release technician, to which ONLY release-blocking bug fixes and corrections to typographical errors will be pushed. The release technician should announce a temporary hold on pushes to the dev branch on the Council list, then create the branch and push it to GitHub using the following commands:" ... "After the release branch has been pushed, the release technician should inform the Council list and ask the maintainers of the TEI Jenkins systems (currently Martin Holmes, Peter Stadler, and James Cummings) to add a build of the release branch."
Thoughts?
Also, the Stylesheets are still their own animal somewhat, and are not covered properly in TCW22 yet. I'm happy to deal with them this go-round and add instructions to TCW22 as I go.