We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up). I've built an HTML version of the current state of the Guidelines at: http://teic.github.io/TEI/index.html I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen. As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc. The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in! Hugh
Has this set of related issues been fixed? <https://github.com/TEIC/oxygen-tei/issues/7> <https://github.com/TEIC/TEI/issues/1447> <https://github.com/TEIC/Stylesheets/issues/176> I think these should really be release-blocking, but that's mainly because they result in an invalid schema being generated from one of my own project ODDs. Cheers, Martin On 2016-12-08 11:27 AM, Hugh Cayless wrote:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there. Should I make a branch for Stylesheets as well? Magdalena 2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh -- 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
Let me take a look at the tickets Martin posted about first. Sent from my phone.
On Dec 8, 2016, at 14:41, Magdalena Turska <tuurma@gmail.com> wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there. Should I make a branch for Stylesheets as well?
Magdalena
2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh -- 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
Have a fix for it. Will probably break all the tests... On Thu, Dec 8, 2016 at 2:58 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Let me take a look at the tickets Martin posted about first.
Sent from my phone.
On Dec 8, 2016, at 14:41, Magdalena Turska <tuurma@gmail.com> wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there. Should I make a branch for Stylesheets as well?
Magdalena
2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh -- 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
Martin, I don't think those tickets are related. The others seem to be about the anyXML/ID conflict thing, which should now be fixed. On Thu, Dec 8, 2016 at 4:44 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Have a fix for it. Will probably break all the tests...
On Thu, Dec 8, 2016 at 2:58 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Let me take a look at the tickets Martin posted about first.
Sent from my phone.
On Dec 8, 2016, at 14:41, Magdalena Turska <tuurma@gmail.com> wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there. Should I make a branch for Stylesheets as well?
Magdalena
2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh -- 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
Good -- I think the tickets got tangled up because they were all a bit mysterious initially, and related to xml:ids. If your fix has worked, please go ahead and close anything that should no longer be open. Cheers, Martin On 2016-12-08 01:59 PM, Hugh Cayless wrote:
Martin, I don't think those tickets are related. The others seem to be about the anyXML/ID conflict thing, which should now be fixed.
On Thu, Dec 8, 2016 at 4:44 PM, Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>> wrote:
Have a fix for it. Will probably break all the tests...
On Thu, Dec 8, 2016 at 2:58 PM, Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>> wrote:
Let me take a look at the tickets Martin posted about first.
Sent from my phone.
> On Dec 8, 2016, at 14:41, Magdalena Turska <tuurma@gmail.com <mailto:tuurma@gmail.com>> wrote: > > Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please > commit all your fixes there. Should I make a branch for Stylesheets as > well? > > Magdalena > > 2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>: > >> We are finally at a point where all of the issues in >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> are closed! I think we can now do >> a >> release branch. Is this something the release techs feel comfortable doing? >> Or would you like me to do it? I'll be away on vacation tomorrow and this >> weekend, so if you want me to do it, please let me know ASAP. Once we have >> release branches for the Guidelines and Stylesheets, we'll need Jenkins >> jobs set up for them too (I'm cc'ing Martin as a heads-up). >> >> I've built an HTML version of the current state of the Guidelines at: >> >> http://teic.github.io/TEI/index.html <http://teic.github.io/TEI/index.html> >> >> I'm trying out some design tweaks here: different fonts, and a few >> additional display changes. Nothing major, just trying to start making it >> look a little more modern. Please let me know what you think. These changes >> have not been committed to the dev branch, so they will not be reflected in >> the release unless we decide to make it happen. >> >> As a reminder, the release documentation is here: >> http://teic.github.io/TCW/tcw22.html <http://teic.github.io/TCW/tcw22.html>, which pulls from this repo: >> https://github.com/TEIC/Documentation <https://github.com/TEIC/Documentation>. We will undoubtedly need to do some >> rewriting on the TCW 22 doc. >> >> The last big task is to finish writing the release notes. I plan to do a >> little work on that before I leave this afternoon, but please do pitch in! >> >> Hugh >> -- >> tei-council mailing list >> tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <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 <mailto:tei-council@lists.tei-c.org> > http://lists.lists.tei-c.org/mailman/listinfo/tei-council <http://lists.lists.tei-c.org/mailman/listinfo/tei-council> > > PLEASE NOTE: postings to this list are publicly archived
Tests pass, so I've closed the issue. Magdalena, when you read this, it's ok to make a Stylesheets release branch too. Thanks! I'll be offline pretty much all day tomorrow, but will read emails later. I didn't get to update the release notes yet I'm afraid. Hugh On Thu, Dec 8, 2016 at 2:41 PM, Magdalena Turska <tuurma@gmail.com> wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there. Should I make a branch for Stylesheets as well?
Magdalena
2016-12-08 19:27 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
We are finally at a point where all of the issues in https://github.com/TEIC/TEI/milestone/2 are closed! I think we can now do a release branch. Is this something the release techs feel comfortable doing? Or would you like me to do it? I'll be away on vacation tomorrow and this weekend, so if you want me to do it, please let me know ASAP. Once we have release branches for the Guidelines and Stylesheets, we'll need Jenkins jobs set up for them too (I'm cc'ing Martin as a heads-up).
I've built an HTML version of the current state of the Guidelines at:
http://teic.github.io/TEI/index.html
I'm trying out some design tweaks here: different fonts, and a few additional display changes. Nothing major, just trying to start making it look a little more modern. Please let me know what you think. These changes have not been committed to the dev branch, so they will not be reflected in the release unless we decide to make it happen.
As a reminder, the release documentation is here: http://teic.github.io/TCW/tcw22.html, which pulls from this repo: https://github.com/TEIC/Documentation. We will undoubtedly need to do some rewriting on the TCW 22 doc.
The last big task is to finish writing the release notes. I plan to do a little work on that before I leave this afternoon, but please do pitch in!
Hugh -- 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
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
And, of course, the release notes. Although I wonder if in future we want to get the release notes wrapped up before making the release branch?
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one. Cheers, Martin On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
Hi Martin, would you please carry on with renaming old branches and point things at 3.1.0? Many thanks! Magdalena 2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca>:
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please
commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
-- 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
Hi Magda and James (and Hugh)-- I remember I volunteered to monitor this release and take notes to help add to the release documentation, just as an observer without being caught up in the process. Would that be helpful? If so, let me know when the fun begins. I remember we identified some rough patches in TCW 22 last round when Syd and I worked on the March release and I *think* those observations were added? Also recall discussions with Martin H. on how this shouldn't have to be a 36-hour vigil if we paced the work differently... Elisa Typeset by hand on my iPad
On Dec 12, 2016, at 5:50 AM, Magdalena Turska <tuurma@gmail.com> wrote:
Hi Martin,
would you please carry on with renaming old branches and point things at 3.1.0? Many thanks!
Magdalena
2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca>:
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please
commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
-- 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
If it's helpful, I can be available for most of my workday on the 15th. I'll be out for a Christmas lunch in the middle. Cheers, Martin On 2016-12-12 05:32 AM, Elisa wrote:
Hi Magda and James (and Hugh)-- I remember I volunteered to monitor this release and take notes to help add to the release documentation, just as an observer without being caught up in the process. Would that be helpful? If so, let me know when the fun begins.
I remember we identified some rough patches in TCW 22 last round when Syd and I worked on the March release and I *think* those observations were added? Also recall discussions with Martin H. on how this shouldn't have to be a 36-hour vigil if we paced the work differently...
Elisa
Typeset by hand on my iPad
On Dec 12, 2016, at 5:50 AM, Magdalena Turska <tuurma@gmail.com <mailto:tuurma@gmail.com>> wrote:
Hi Martin,
would you please carry on with renaming old branches and point things at 3.1.0? Many thanks!
Magdalena
2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>>:
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please
commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
-- tei-council mailing list tei-council@lists.tei-c.org <mailto: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 <mailto: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
My bad, thanks for pointing this out, Martin. Fixed now. 2016-12-12 16:56 GMT+00:00 Martin Holmes <mholmes@uvic.ca>:
If it's helpful, I can be available for most of my workday on the 15th. I'll be out for a Christmas lunch in the middle.
Cheers, Martin
On 2016-12-12 05:32 AM, Elisa wrote:
Hi Magda and James (and Hugh)-- I remember I volunteered to monitor this release and take notes to help add to the release documentation, just as an observer without being caught up in the process. Would that be helpful? If so, let me know when the fun begins.
I remember we identified some rough patches in TCW 22 last round when Syd and I worked on the March release and I *think* those observations were added? Also recall discussions with Martin H. on how this shouldn't have to be a 36-hour vigil if we paced the work differently...
Elisa
Typeset by hand on my iPad
On Dec 12, 2016, at 5:50 AM, Magdalena Turska <tuurma@gmail.com <mailto:tuurma@gmail.com>> wrote:
Hi Martin,
would you please carry on with renaming old branches and point things at 3.1.0? Many thanks!
Magdalena
2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>>:
When the Stylesheets branch is made, I'll rename the old release branches
on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so
please
commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
--
tei-council mailing list tei-council@lists.tei-c.org <mailto: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 <mailto: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
All set up. Stylesheets are building now. Fingers crossed. :-) Cheers, Martin On 2016-12-12 09:28 AM, Magdalena Turska wrote:
My bad, thanks for pointing this out, Martin. Fixed now.
2016-12-12 16:56 GMT+00:00 Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>>:
If it's helpful, I can be available for most of my workday on the 15th. I'll be out for a Christmas lunch in the middle.
Cheers, Martin
On 2016-12-12 05:32 AM, Elisa wrote:
Hi Magda and James (and Hugh)-- I remember I volunteered to monitor this release and take notes to help add to the release documentation, just as an observer without being caught up in the process. Would that be helpful? If so, let me know when the fun begins.
I remember we identified some rough patches in TCW 22 last round when Syd and I worked on the March release and I *think* those observations were added? Also recall discussions with Martin H. on how this shouldn't have to be a 36-hour vigil if we paced the work differently...
Elisa
Typeset by hand on my iPad
On Dec 12, 2016, at 5:50 AM, Magdalena Turska <tuurma@gmail.com <mailto:tuurma@gmail.com> <mailto:tuurma@gmail.com <mailto:tuurma@gmail.com>>> wrote:
Hi Martin,
would you please carry on with renaming old branches and point things at 3.1.0? Many thanks!
Magdalena
2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca> <mailto:mholmes@uvic.ca <mailto:mholmes@uvic.ca>>>:
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please
commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
--
tei-council mailing list tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> <mailto:tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <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 <mailto:tei-council@lists.tei-c.org> <mailto:tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <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 <mailto:tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <http://lists.lists.tei-c.org/mailman/listinfo/tei-council>
PLEASE NOTE: postings to this list are publicly archived
Hi Magdalena, The Stylesheets branch seems to be wrongly named; it's: release-3.1.0 just like the P5 branch, but Stylesheets version numbering is in the 7s at this point. The last release was: release-7.41.0 so I think the next one should be named release-7.42.0 which accords with the content of the VERSION document: <https://github.com/TEIC/Stylesheets/blob/dev/VERSION> Cheers, Martin On 2016-12-12 02:50 AM, Magdalena Turska wrote:
Hi Martin,
would you please carry on with renaming old branches and point things at 3.1.0? Many thanks!
Magdalena
2016-12-09 16:15 GMT+00:00 Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>>:
When the Stylesheets branch is made, I'll rename the old release branches on teijenkins and point them at release-3.1.0 and the Stylesheets one.
Cheers, Martin
On 2016-12-09 08:03 AM, Syd Bauman wrote:
Just pushed release-3.1.0 branch for the Guidelines into gitHub, so please commit all your fixes there.
Only fixes to release-blocking issues or fixes that are minor enough as to not need testing (like correcting a typo in the prose) should go to the release-3.1.0 branch. Everything else should go to dev, as usual.
Should I make a branch for Stylesheets as well?
Please let us know when you do.
-- tei-council mailing list tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council <http://lists.lists.tei-c.org/mailman/listinfo/tei-council>
PLEASE NOTE: postings to this list are publicly archived
participants (5)
-
Elisa -
Hugh Cayless -
Magdalena Turska -
Martin Holmes -
Syd Bauman