Re: [tei-council] shivering ...

Agreed. My own feeling is that if any substantive work has been done on the Stylesheets during the course of a release cycle, then a TEI release probably warrants a Stylesheets release; a Stylesheets release can happen at any time and would hardly ever warrant a TEI release. The two are tightly coupled with regard to the generation of Schemas from ODDs and the generation of the Guidelines themselves, of course, and changes to that code mean a TEI release has to have a concurrent Stylesheets release. We’re in this situation now, because of the Pure ODD changes to the Stylesheets. We need to have a policy for evaluating when to release the Stylesheets, and this isn’t covered at all in the current documentation, which is why I’d asked the release technicians not to do anything for the Stylesheets yet. I think for this round, I should play the role of Stylesheets maintainer as that role appears in TCW22, and then we can debrief and write some Stylesheets release documentation at the F2F. I’ve deleted the release-3.0.0 branch in the Stylesheets repo and will add a new, correctly named one.

On Mar 17, 2016, at 7:35 , Lou Burnard wrote:

I'd say the new release of the Stylesheets should be 7.41.0

It definitely shouldnt have the same version number as the next release of the Guidelines, since Stylesheets releases are not necessarily tied into GL release (this one is because several of the new features in the GL necessitated Stylesheet modifications, but that isn't usually the case).

And it shouldnt be an 8.0.0 till we do a really major revision

On 17/03/16 00:41, Syd Bauman wrote:

...

Done. HOWEVER, we did not know what the release # of the stylesheets should be, so we called the new release branch in Stylesheets "release-3.0.0", too (which it isn't -- it's either 7.40.1, or 7.41.0, or 8.0.0, or whatever). But I wanted to have a separate release branch available at the same time. As soon as I can figure out the correct release # (or someone tells me) we can re-name that branch.

In the meantime, please do work for the upcoming release in the "release-3.0.0" branch (do `git pull` then `git checkout release-3.0.0`). Do work not intended for the upcoming release in 'dev', as usual.

-- Syd & Elisa

...

Elisa and I are about to do the "branch dev to release" bit. So it would be prudent to hold off on comitting anything for the next 10-20 mins or whatever.

-- 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