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.
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.
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.
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
I just set up Jenkins jobs (suffixed with „_release_branch") for the release branch: http://jenkins-paderborn.tei-c.org/ Let me know when there is a release branch for the Stylesheets again and I will adjust the jobs appropriately (currently the Guidelines are built with the Stylesheets dev branch) Best Peter
Am 17.03.2016 um 13:00 schrieb Hugh Cayless
: 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
-- 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
Thanks Peter!
release-7.41.0 is up on https://github.com/TEIC/Stylesheets now.
On Thu, Mar 17, 2016 at 8:28 AM, Peter Stadler
I just set up Jenkins jobs (suffixed with „_release_branch") for the release branch: http://jenkins-paderborn.tei-c.org/
Let me know when there is a release branch for the Stylesheets again and I will adjust the jobs appropriately (currently the Guidelines are built with the Stylesheets dev branch)
Best Peter
Am 17.03.2016 um 13:00 schrieb Hugh Cayless
: 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
-- 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
-- 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
Dear Hugh, I'm sorry that we ignored your request to leave the Stylesheets alone, which we simply did not recall at the time we were working through and thinking about the instructions at TCW22. It wasn't intentional--but definitely a sign of how much is murky surrounding the Stylesheets. I was poring over recent messages to do with the release and that message, though I do dimly remember your saying to wait on the Stylesheets--a week ago, maybe? The flurry of activity this week over tickets seems to have eclipsed it for us. Anyway, yes, please--more information on the Stylesheets and how their release should or should not be associated with the Guidelines would be very helpful. Best, Elisa Typeset by hand on my iPad
On Mar 17, 2016, at 8:00 AM, Hugh Cayless
wrote: 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
-- 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
It's not a big deal. The Stylesheets are murky because prior to a few
months ago we could just depend on handing responsibility off to Sebastian,
so this is new territory for the saddest of reasons.
In my ideal world, TCW22 should require no interpretation at all, it would
be easy to follow and you'd just do what it told you. We're not there yet,
but maybe we can get there :-).
On Thu, Mar 17, 2016 at 8:57 AM, Elisa
Dear Hugh, I'm sorry that we ignored your request to leave the Stylesheets alone, which we simply did not recall at the time we were working through and thinking about the instructions at TCW22. It wasn't intentional--but definitely a sign of how much is murky surrounding the Stylesheets. I was poring over recent messages to do with the release and that message, though I do dimly remember your saying to wait on the Stylesheets--a week ago, maybe? The flurry of activity this week over tickets seems to have eclipsed it for us. Anyway, yes, please--more information on the Stylesheets and how their release should or should not be associated with the Guidelines would be very helpful.
Best, Elisa Typeset by hand on my iPad
On Mar 17, 2016, at 8:00 AM, Hugh Cayless
wrote: 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
-- 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 -- 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
participants (5)
-
Elisa
-
Hugh Cayless
-
Lou Burnard
-
Peter Stadler
-
Syd Bauman