Given that we were supposed to make a release branch last week, it seems safe to say we're not ready to go :-). https://github.com/TEIC/TEI/milestone/2 shows 7 open tickets, including the showstopper one flagged by Syd and Lou. I'm presuming we should push the release date back. Does anyone need help? James and Magdalena, what do you need from us?
Hi Hugh, Sorry, things have been very busy for me at the moment here. (Everyone has noticed that the end of the calendar year is coming and they suddenly have cropped up wanting everything finished before then.) I think the work and prose for the att.global.source is done. Lou was starting to test that branch, but if someone could and get it merged in, that'd be good to get that one off the docket. I think the Lou/Syd @maxOccurs (where I think the default should be assumed to be unbounded but I've not been closely following the discussion) is the real release blocker. There are a couple there that are still marked Needs Discussion, if that is the case then those should be postponed to next release. If we need to push the date back (so that people can solve these problems, test everything builds, check prose, etc.) then I am also potentially available for most of the 13/14/15/19/20/21 but don't know Magdalena's schedule. Other than solving those problems, merging those branches, then adding notes to the release notes if you've implemented _anything_ since January. -James On 30/11/16 17:39, Hugh Cayless wrote:
Given that we were supposed to make a release branch last week, it seems safe to say we're not ready to go :-). https://github.com/TEIC/TEI/milestone/2 shows 7 open tickets, including the showstopper one flagged by Syd and Lou. I'm presuming we should push the release date back. Does anyone need help? James and Magdalena, what do you need from us?
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch? On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk> wrote:
Hi Hugh,
Sorry, things have been very busy for me at the moment here. (Everyone has noticed that the end of the calendar year is coming and they suddenly have cropped up wanting everything finished before then.)
I think the work and prose for the att.global.source is done. Lou was starting to test that branch, but if someone could and get it merged in, that'd be good to get that one off the docket. I think the Lou/Syd @maxOccurs (where I think the default should be assumed to be unbounded but I've not been closely following the discussion) is the real release blocker. There are a couple there that are still marked Needs Discussion, if that is the case then those should be postponed to next release.
If we need to push the date back (so that people can solve these problems, test everything builds, check prose, etc.) then I am also potentially available for most of the 13/14/15/19/20/21 but don't know Magdalena's schedule.
Other than solving those problems, merging those branches, then adding notes to the release notes if you've implemented _anything_ since January.
-James
On 30/11/16 17:39, Hugh Cayless wrote:
Given that we were supposed to make a release branch last week, it seems safe to say we're not ready to go :-). https://github.com/TEIC/TEI/milestone/2 shows 7 open tickets, including the showstopper one flagged by Syd and Lou. I'm presuming we should push the release date back. Does anyone need help? James and Magdalena, what do you need from us?
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
-- 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 to answer James' timing question, his dates would work for me, except for Friday 16th 2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings < James.Cummings@it.ox.ac.uk> wrote:
Hi Hugh,
Sorry, things have been very busy for me at the moment here. (Everyone has noticed that the end of the calendar year is coming and they suddenly have cropped up wanting everything finished before then.)
I think the work and prose for the att.global.source is done. Lou was starting to test that branch, but if someone could and get it merged in, that'd be good to get that one off the docket. I think the Lou/Syd @maxOccurs (where I think the default should be assumed to be unbounded but I've not been closely following the discussion) is the real release blocker. There are a couple there that are still marked Needs Discussion, if that is the case then those should be postponed to next release.
If we need to push the date back (so that people can solve these problems, test everything builds, check prose, etc.) then I am also potentially available for most of the 13/14/15/19/20/21 but don't know Magdalena's schedule.
Other than solving those problems, merging those branches, then adding notes to the release notes if you've implemented _anything_ since January.
-James
On 30/11/16 17:39, Hugh Cayless wrote:
Given that we were supposed to make a release branch last week, it seems safe to say we're not ready to go :-). https://github.com/TEIC/TEI/milestone/2 shows 7 open tickets, including the showstopper one flagged by Syd and Lou. I'm presuming we should push the release date back. Does anyone need help? James and Magdalena, what do you need from us?
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
-- 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
I think it's a bad idea to release on a Friday anyway :-) I've merged the att.global.source branch. Let's see if Jenkins likes it. FYI, I did: git fetch --all (to make sure I had all the remote branches) git checkout att.global.source git rebase dev (git merge dev would work too--rebase seemed fairly safe in this case) git checkout dev git merge att.global.source On Fri, Dec 2, 2016 at 12:14 PM, Magdalena Turska <tuurma@gmail.com> wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings < James.Cummings@it.ox.ac.uk> wrote:
Hi Hugh,
Sorry, things have been very busy for me at the moment here. (Everyone has noticed that the end of the calendar year is coming and they suddenly have cropped up wanting everything finished before then.)
I think the work and prose for the att.global.source is done. Lou was starting to test that branch, but if someone could and get it merged in, that'd be good to get that one off the docket. I think the Lou/Syd @maxOccurs (where I think the default should be assumed to be unbounded but I've not been closely following the discussion) is the real release blocker. There are a couple there that are still marked Needs Discussion, if that is the case then those should be postponed to next release.
If we need to push the date back (so that people can solve these problems, test everything builds, check prose, etc.) then I am also potentially available for most of the 13/14/15/19/20/21 but don't know Magdalena's schedule.
Other than solving those problems, merging those branches, then adding notes to the release notes if you've implemented _anything_ since January.
-James
On 30/11/16 17:39, Hugh Cayless wrote:
Given that we were supposed to make a release branch last week, it seems safe to say we're not ready to go :-). https://github.com/TEIC/TEI/milestone/2 shows 7 open tickets, including the showstopper one flagged by Syd and Lou. I'm presuming we should push the release date back. Does anyone need help? James and Magdalena, what do you need from us?
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
-- 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
Hi all, It looks like the att.global.source branch is merged in successfully, and Lou's changes to the prose seem good to me. I've tested in RNG but nothing else yet. Trusting that the min/max problem Syd and others have been looking at will be solved soon if it isn't already (If it was just DTDs having a problem you know know what I'd say!). What do people think of Thursday 15 December as a release date? I have a couple meetings during the day but if we start early and others are on hand to help with the inevitable problems then it should be fine. I worry most about some Stylesheet, Roma, or OxGarage related problem to be honest. Magdalena: Are you available that day? Others, can you be around for some of it? (I've CC'd MartinH not only as the lead jenkins.tei-c.org maintainer but also as someone who may want to be around later in the day.) Let's assume that there should be no new schema-modifying changes (except if needed to solve release-blocking problems) but that corrections to prose is still allowed (typos etc.) so a *chill*. -James On 02/12/16 17:14, Magdalena Turska wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote:
> Hi Hugh, > > Sorry, things have been very busy for me at the moment here. (Everyone has > noticed that the end of the calendar year is coming and they suddenly have > cropped up wanting everything finished before then.) > > I think the work and prose for the att.global.source is done. Lou was > starting to test that branch, but if someone could and get it merged in, > that'd be good to get that one off the docket. I think the Lou/Syd > @maxOccurs (where I think the default should be assumed to be unbounded but > I've not been closely following the discussion) is the real release > blocker. There are a couple there that are still marked Needs Discussion, > if that is the case then those should be postponed to next release. > > If we need to push the date back (so that people can solve these problems, > test everything builds, check prose, etc.) then I am also potentially > available for most of the 13/14/15/19/20/21 but don't know Magdalena's > schedule. > > Other than solving those problems, merging those branches, then adding > notes to the release notes if you've implemented _anything_ since January. > > -James > > > > On 30/11/16 17:39, Hugh Cayless wrote: > >> Given that we were supposed to make a release branch last week, it seems >> safe to say we're not ready to go :-). >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> shows 7 open tickets, including >> the >> showstopper one flagged by Syd and Lou. I'm presuming we should push the >> release date back. Does anyone need help? James and Magdalena, what do you >> need from us? >> > > > -- > Dr James Cummings, James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> > Academic IT Services, University of Oxford > > -- > 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
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford
I'm pretty sure there's still one release-blocker: <https://github.com/TEIC/Stylesheets/issues/190> That breaks the bleeding-edge oxygen-tei plugin, and will cause havoc if it's still broken when the next Oxygen release comes out. For us to address it means, I think, integrating the latest Saxon into build processes for both Stylesheets and TEI, and fixing everything that breaks. I think there may be more than one problem that's revealed as a result of stricter rules in the new Saxon. Cheers, Martin On 2016-12-03 01:12 PM, James Cummings wrote:
Hi all, It looks like the att.global.source branch is merged in successfully, and Lou's changes to the prose seem good to me. I've tested in RNG but nothing else yet. Trusting that the min/max problem Syd and others have been looking at will be solved soon if it isn't already (If it was just DTDs having a problem you know know what I'd say!). What do people think of Thursday 15 December as a release date? I have a couple meetings during the day but if we start early and others are on hand to help with the inevitable problems then it should be fine. I worry most about some Stylesheet, Roma, or OxGarage related problem to be honest.
Magdalena: Are you available that day? Others, can you be around for some of it? (I've CC'd MartinH not only as the lead jenkins.tei-c.org maintainer but also as someone who may want to be around later in the day.)
Let's assume that there should be no new schema-modifying changes (except if needed to solve release-blocking problems) but that corrections to prose is still allowed (typos etc.) so a *chill*.
-James
On 02/12/16 17:14, Magdalena Turska wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote:
> Hi Hugh, > > Sorry, things have been very busy for me at the moment here. (Everyone has > noticed that the end of the calendar year is coming and they suddenly have > cropped up wanting everything finished before then.) > > I think the work and prose for the att.global.source is done. Lou was > starting to test that branch, but if someone could and get it merged in, > that'd be good to get that one off the docket. I think the Lou/Syd > @maxOccurs (where I think the default should be assumed to be unbounded but > I've not been closely following the discussion) is the real release > blocker. There are a couple there that are still marked Needs Discussion, > if that is the case then those should be postponed to next release. > > If we need to push the date back (so that people can solve these problems, > test everything builds, check prose, etc.) then I am also potentially > available for most of the 13/14/15/19/20/21 but don't know Magdalena's > schedule. > > Other than solving those problems, merging those branches, then adding > notes to the release notes if you've implemented _anything_ since January. > > -James > > > > On 30/11/16 17:39, Hugh Cayless wrote: > >> Given that we were supposed to make a release branch last week, it seems >> safe to say we're not ready to go :-). >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> shows 7 open tickets, including >> the >> showstopper one flagged by Syd and Lou. I'm presuming we should push the >> release date back. Does anyone need help? James and Magdalena, what do you >> need from us? >> > > > -- > Dr James Cummings, James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> > Academic IT Services, University of Oxford > > -- > 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
Yeah, that looks most thoroughly hosed, using the latest Saxon HE release. Looking into it.... On Sat, Dec 3, 2016 at 5:53 PM, Martin Holmes <mholmes@uvic.ca> wrote:
I'm pretty sure there's still one release-blocker:
<https://github.com/TEIC/Stylesheets/issues/190>
That breaks the bleeding-edge oxygen-tei plugin, and will cause havoc if it's still broken when the next Oxygen release comes out. For us to address it means, I think, integrating the latest Saxon into build processes for both Stylesheets and TEI, and fixing everything that breaks.
I think there may be more than one problem that's revealed as a result of stricter rules in the new Saxon.
Cheers, Martin
On 2016-12-03 01:12 PM, James Cummings wrote:
Hi all, It looks like the att.global.source branch is merged in successfully, and Lou's changes to the prose seem good to me. I've tested in RNG but nothing else yet. Trusting that the min/max problem Syd and others have been looking at will be solved soon if it isn't already (If it was just DTDs having a problem you know know what I'd say!). What do people think of Thursday 15 December as a release date? I have a couple meetings during the day but if we start early and others are on hand to help with the inevitable problems then it should be fine. I worry most about some Stylesheet, Roma, or OxGarage related problem to be honest.
Magdalena: Are you available that day? Others, can you be around for some of it? (I've CC'd MartinH not only as the lead jenkins.tei-c.org maintainer but also as someone who may want to be around later in the day.)
Let's assume that there should be no new schema-modifying changes (except if needed to solve release-blocking problems) but that corrections to prose is still allowed (typos etc.) so a *chill*.
-James
On 02/12/16 17:14, Magdalena Turska wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote:
> Hi Hugh, > > Sorry, things have been very busy for me at the moment here. (Everyone has > noticed that the end of the calendar year is coming and they suddenly have > cropped up wanting everything finished before then.) > > I think the work and prose for the att.global.source is done. Lou was > starting to test that branch, but if someone could and get it merged in, > that'd be good to get that one off the docket. I think the Lou/Syd > @maxOccurs (where I think the default should be assumed to be unbounded but > I've not been closely following the discussion) is the real release > blocker. There are a couple there that are still marked Needs Discussion, > if that is the case then those should be postponed to next release. > > If we need to push the date back (so that people can solve these problems, > test everything builds, check prose, etc.) then I am also potentially > available for most of the 13/14/15/19/20/21 but don't know Magdalena's > schedule. > > Other than solving those problems, merging those branches, then adding > notes to the release notes if you've implemented _anything_ since January. > > -James > > > > On 30/11/16 17:39, Hugh Cayless wrote: > >> Given that we were supposed to make a release branch last week, it seems >> safe to say we're not ready to go :-). >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> shows 7 open tickets, including >> the >> showstopper one flagged by Syd and Lou. I'm presuming we should push the >> release date back. Does anyone need help? James and Magdalena, what do you >> need from us? >> > > > -- > Dr James Cummings, James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> > Academic IT Services, University of Oxford > > -- > 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
--
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
Most annoyingly, the latest version of Saxon seems to have a new algorithm for generating ids, so all the expected results in the Test directory are off. On Sun, Dec 4, 2016 at 7:29 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Yeah, that looks most thoroughly hosed, using the latest Saxon HE release. Looking into it....
On Sat, Dec 3, 2016 at 5:53 PM, Martin Holmes <mholmes@uvic.ca> wrote:
I'm pretty sure there's still one release-blocker:
<https://github.com/TEIC/Stylesheets/issues/190>
That breaks the bleeding-edge oxygen-tei plugin, and will cause havoc if it's still broken when the next Oxygen release comes out. For us to address it means, I think, integrating the latest Saxon into build processes for both Stylesheets and TEI, and fixing everything that breaks.
I think there may be more than one problem that's revealed as a result of stricter rules in the new Saxon.
Cheers, Martin
On 2016-12-03 01:12 PM, James Cummings wrote:
Hi all, It looks like the att.global.source branch is merged in successfully, and Lou's changes to the prose seem good to me. I've tested in RNG but nothing else yet. Trusting that the min/max problem Syd and others have been looking at will be solved soon if it isn't already (If it was just DTDs having a problem you know know what I'd say!). What do people think of Thursday 15 December as a release date? I have a couple meetings during the day but if we start early and others are on hand to help with the inevitable problems then it should be fine. I worry most about some Stylesheet, Roma, or OxGarage related problem to be honest.
Magdalena: Are you available that day? Others, can you be around for some of it? (I've CC'd MartinH not only as the lead jenkins.tei-c.org maintainer but also as someone who may want to be around later in the day.)
Let's assume that there should be no new schema-modifying changes (except if needed to solve release-blocking problems) but that corrections to prose is still allowed (typos etc.) so a *chill*.
-James
On 02/12/16 17:14, Magdalena Turska wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote:
> Hi Hugh, > > Sorry, things have been very busy for me at the moment here. (Everyone has > noticed that the end of the calendar year is coming and they suddenly have > cropped up wanting everything finished before then.) > > I think the work and prose for the att.global.source is done. Lou was > starting to test that branch, but if someone could and get it merged in, > that'd be good to get that one off the docket. I think the Lou/Syd > @maxOccurs (where I think the default should be assumed to be unbounded but > I've not been closely following the discussion) is the real release > blocker. There are a couple there that are still marked Needs Discussion, > if that is the case then those should be postponed to next release. > > If we need to push the date back (so that people can solve these problems, > test everything builds, check prose, etc.) then I am also potentially > available for most of the 13/14/15/19/20/21 but don't know Magdalena's > schedule. > > Other than solving those problems, merging those branches, then adding > notes to the release notes if you've implemented _anything_ since January. > > -James > > > > On 30/11/16 17:39, Hugh Cayless wrote: > >> Given that we were supposed to make a release branch last week, it seems >> safe to say we're not ready to go :-). >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> shows 7 open tickets, including >> the >> showstopper one flagged by Syd and Lou. I'm presuming we should push the >> release date back. Does anyone need help? James and Magdalena, what do you >> need from us? >> > > > -- > Dr James Cummings, James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> > Academic IT Services, University of Oxford > > -- > 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
--
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
Think I've almost got it. Tests are passing now. The full build might still break, but if this last test run succeeds, I'll push the changes and we'll see. On Sun, Dec 4, 2016 at 8:21 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Most annoyingly, the latest version of Saxon seems to have a new algorithm for generating ids, so all the expected results in the Test directory are off.
On Sun, Dec 4, 2016 at 7:29 PM, Hugh Cayless <philomousos@gmail.com> wrote:
Yeah, that looks most thoroughly hosed, using the latest Saxon HE release. Looking into it....
On Sat, Dec 3, 2016 at 5:53 PM, Martin Holmes <mholmes@uvic.ca> wrote:
I'm pretty sure there's still one release-blocker:
<https://github.com/TEIC/Stylesheets/issues/190>
That breaks the bleeding-edge oxygen-tei plugin, and will cause havoc if it's still broken when the next Oxygen release comes out. For us to address it means, I think, integrating the latest Saxon into build processes for both Stylesheets and TEI, and fixing everything that breaks.
I think there may be more than one problem that's revealed as a result of stricter rules in the new Saxon.
Cheers, Martin
On 2016-12-03 01:12 PM, James Cummings wrote:
Hi all, It looks like the att.global.source branch is merged in successfully, and Lou's changes to the prose seem good to me. I've tested in RNG but nothing else yet. Trusting that the min/max problem Syd and others have been looking at will be solved soon if it isn't already (If it was just DTDs having a problem you know know what I'd say!). What do people think of Thursday 15 December as a release date? I have a couple meetings during the day but if we start early and others are on hand to help with the inevitable problems then it should be fine. I worry most about some Stylesheet, Roma, or OxGarage related problem to be honest.
Magdalena: Are you available that day? Others, can you be around for some of it? (I've CC'd MartinH not only as the lead jenkins.tei-c.org maintainer but also as someone who may want to be around later in the day.)
Let's assume that there should be no new schema-modifying changes (except if needed to solve release-blocking problems) but that corrections to prose is still allowed (typos etc.) so a *chill*.
-James
On 02/12/16 17:14, Magdalena Turska wrote:
Just to answer James' timing question, his dates would work for me, except for Friday 16th
2016-12-02 17:06 GMT+00:00 Hugh Cayless <philomousos@gmail.com <mailto:philomousos@gmail.com>>:
I can merge it if no-one's done it yet. What about the max/minOccurs thing? Is there a fix in the works Syd? When can we create a release branch?
On Wed, Nov 30, 2016 at 2:09 PM, James Cummings <James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk>> wrote:
> Hi Hugh, > > Sorry, things have been very busy for me at the moment here. (Everyone has > noticed that the end of the calendar year is coming and they suddenly have > cropped up wanting everything finished before then.) > > I think the work and prose for the att.global.source is done. Lou was > starting to test that branch, but if someone could and get it merged in, > that'd be good to get that one off the docket. I think the Lou/Syd > @maxOccurs (where I think the default should be assumed to be unbounded but > I've not been closely following the discussion) is the real release > blocker. There are a couple there that are still marked Needs Discussion, > if that is the case then those should be postponed to next release. > > If we need to push the date back (so that people can solve these problems, > test everything builds, check prose, etc.) then I am also potentially > available for most of the 13/14/15/19/20/21 but don't know Magdalena's > schedule. > > Other than solving those problems, merging those branches, then adding > notes to the release notes if you've implemented _anything_ since January. > > -James > > > > On 30/11/16 17:39, Hugh Cayless wrote: > >> Given that we were supposed to make a release branch last week, it seems >> safe to say we're not ready to go :-). >> https://github.com/TEIC/TEI/milestone/2 <https://github.com/TEIC/TEI/milestone/2> shows 7 open tickets, including >> the >> showstopper one flagged by Syd and Lou. I'm presuming we should push the >> release date back. Does anyone need help? James and Magdalena, what do you >> need from us? >> > > > -- > Dr James Cummings, James.Cummings@it.ox.ac.uk <mailto:James.Cummings@it.ox.ac.uk> > Academic IT Services, University of Oxford > > -- > 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
--
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 (4)
-
Hugh Cayless -
James Cummings -
Magdalena Turska -
Martin Holmes