Condensing (or compressing) Refrigeration?
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release? Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment. I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week. But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now? Also, I will be flying to Utrecht to arrive for DH2019 on 6 July. Best, Elisa Sent from my iPhone
The dev branch is basically ok now, I think. There's one warning being triggered on the JTEI exemplar, and I'm not sure whether that's a real warning or one that should be ignored. Jenkins is happy, but Jenkins2 (which hasn't been updated yet) is not. Given that the build was only fixed last night, I'd be sympathetic to compressing or pushing back the release timeframe. The real question in my mind is whether we ought to delay the release... Hugh On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com> wrote:
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment.
I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week.
But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now?
Also, I will be flying to Utrecht to arrive for DH2019 on 6 July.
Best, Elisa
Sent from my iPhone _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point. Cheers, Martin On 2019-07-02 6:55 a.m., Hugh Cayless wrote:
The dev branch is basically ok now, I think. There's one warning being triggered on the JTEI exemplar, and I'm not sure whether that's a real warning or one that should be ignored. Jenkins is happy, but Jenkins2 (which hasn't been updated yet) is not. Given that the build was only fixed last night, I'd be sympathetic to compressing or pushing back the release timeframe. The real question in my mind is whether we ought to delay the release...
Hugh
On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com>> wrote:
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment.
I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week.
But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now?
Also, I will be flying to Utrecht to arrive for DH2019 on 6 July.
Best, Elisa
Sent from my iPhone _______________________________________________ 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
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre
As I understand it, they shouldn't affect oxGarage, since oxGarage is rarely used to do a build of the entire Guidelines, and associated test suite! And if it were, we'd probably want to stop it. On 02/07/2019 17:54, Martin Holmes wrote:
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point.
Cheers, Martin
On 2019-07-02 6:55 a.m., Hugh Cayless wrote:
The dev branch is basically ok now, I think. There's one warning being triggered on the JTEI exemplar, and I'm not sure whether that's a real warning or one that should be ignored. Jenkins is happy, but Jenkins2 (which hasn't been updated yet) is not. Given that the build was only fixed last night, I'd be sympathetic to compressing or pushing back the release timeframe. The real question in my mind is whether we ought to delay the release...
Hugh
On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com>> wrote:
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment.
I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week.
But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now?
Also, I will be flying to Utrecht to arrive for DH2019 on 6 July.
Best, Elisa
Sent from my iPhone _______________________________________________ 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
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
My point was that if tei-c.org is prone to refusing multiple requests for individual files, then anyone using the Stylesheets to build an ODD might hit the problem by repeatedly requesting (say) p5subset.xml. If OxGarage got a lot of use by a class, for example, all doing the same conversions repeatedly, 429s might start happening. I don't know how the server is configured, though, so maybe p5subset.xml is immune, and it's just these rather unusual SVG and MathML files that are afflicted. Cheers, Martin On 2019-07-02 10:27 a.m., Lou Burnard wrote:
As I understand it, they shouldn't affect oxGarage, since oxGarage is rarely used to do a build of the entire Guidelines, and associated test suite! And if it were, we'd probably want to stop it.
On 02/07/2019 17:54, Martin Holmes wrote:
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point.
Cheers, Martin
On 2019-07-02 6:55 a.m., Hugh Cayless wrote:
The dev branch is basically ok now, I think. There's one warning being triggered on the JTEI exemplar, and I'm not sure whether that's a real warning or one that should be ignored. Jenkins is happy, but Jenkins2 (which hasn't been updated yet) is not. Given that the build was only fixed last night, I'd be sympathetic to compressing or pushing back the release timeframe. The real question in my mind is whether we ought to delay the release...
Hugh
On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com>> wrote:
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment.
I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week.
But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now?
Also, I will be flying to Utrecht to arrive for DH2019 on 6 July.
Best, Elisa
Sent from my iPhone _______________________________________________ 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
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre
I *think* if you just add the "ant-optional" package, the catalog resolution will just start to work. That's what Peter found when working with the Docker-based version of Jenkins. On Tue, Jul 2, 2019 at 12:54 PM Martin Holmes <mholmes@uvic.ca> wrote:
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point.
Cheers, Martin
On 2019-07-02 6:55 a.m., Hugh Cayless wrote:
The dev branch is basically ok now, I think. There's one warning being triggered on the JTEI exemplar, and I'm not sure whether that's a real warning or one that should be ignored. Jenkins is happy, but Jenkins2 (which hasn't been updated yet) is not. Given that the build was only fixed last night, I'd be sympathetic to compressing or pushing back the release timeframe. The real question in my mind is whether we ought to delay the release...
Hugh
On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com>> wrote:
Dear Councillors, My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Here are some timing issues and updates. I have communicated with my original release tech partner, Vanessa, and we agreed that, given the lack of time she has had lately to work with us and concentrate on the TEI, that it is best she defer being a release tech until another time. As I see it, too, I expect this release to be challenging—I am expecting the unexpected—because of all the server issues recently and because the dev branch is still unstable with all the unwanted excitement over the simplePrint ODD. Vanessa asked me to convey her sincere apologies to Council for her absences and lack of time. I hope after the season of deep preoccupation and sadness that she will rejoin us with all the energy I know she has, but now is not the moment.
I am thankful to Magdalena for volunteering to host me near Warsaw after the DH2019 conference next week, and she agreed that the two of us will be the release techs. As we look at prepping this next release, timing now really depends on both of us. I’m visiting her from 13-20 July—and I think Magdalena has her own travel plans starting (Saturday) 20 July. I think we’re safest if things go wrong to make sure we do the release in the middle of that week.
But it sounds like we’re still heatedly coding toward this release, so I’d like to take stock of what we can complete just now—and reset the Refrigeration period, also perhaps scale back on some maybe too ambitious things we thought we could feasibly complete so we can properly refrigerate. Thoughts? What’s the state of the dev branch just now?
Also, I will be flying to Utrecht to arrive for DH2019 on 6 July.
Best, Elisa
Sent from my iPhone _______________________________________________ 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
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
Ah, right. I've installed it and kicked off a fresh build. Cheers, Martin On 2019-07-02 10:38 a.m., Hugh Cayless wrote:
I *think* if you just add the "ant-optional" package, the catalog resolution will just start to work. That's what Peter found when working with the Docker-based version of Jenkins.
On Tue, Jul 2, 2019 at 12:54 PM Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>> wrote:
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point.
Cheers, Martin
On 2019-07-02 6:55 a.m., Hugh Cayless wrote: > The dev branch is basically ok now, I think. There's one warning being > triggered on the JTEI exemplar, and I'm not sure whether that's a real > warning or one that should be ignored. Jenkins is happy, but Jenkins2 > (which hasn't been updated yet) is not. Given that the build was only > fixed last night, I'd be sympathetic to compressing or pushing back the > release timeframe. The real question in my mind is whether we ought to > delay the release... > > Hugh > > On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com> > <mailto:ebbondar@gmail.com <mailto:ebbondar@gmail.com>>> wrote: > > Dear Councillors, > My calendar tells me we have entered the Refrigeration period > leading to the Freeze scheduled for 9 July next week. I have seen > that Refrigeration is often, ironically, a moment of heated work as > we try to resolve big issues and introduce something we care about > for the next release. I am trying that now with the long overdue > Measurement code (unitDecl, unitDef, etc), which really ought to be > coming out. I see intense activity with uniHan right now and wonder > if that too is targeted for this release? > > Here are some timing issues and updates. I have communicated with my > original release tech partner, Vanessa, and we agreed that, given > the lack of time she has had lately to work with us and concentrate > on the TEI, that it is best she defer being a release tech until > another time. As I see it, too, I expect this release to be > challenging—I am expecting the unexpected—because of all the server > issues recently and because the dev branch is still unstable with > all the unwanted excitement over the simplePrint ODD. Vanessa asked > me to convey her sincere apologies to Council for her absences and > lack of time. I hope after the season of deep preoccupation and > sadness that she will rejoin us with all the energy I know she has, > but now is not the moment. > > I am thankful to Magdalena for volunteering to host me near Warsaw > after the DH2019 conference next week, and she agreed that the two > of us will be the release techs. As we look at prepping this next > release, timing now really depends on both of us. I’m visiting her > from 13-20 July—and I think Magdalena has her own travel plans > starting (Saturday) 20 July. I think we’re safest if things go wrong > to make sure we do the release in the middle of that week. > > But it sounds like we’re still heatedly coding toward this release, > so I’d like to take stock of what we can complete just now—and reset > the Refrigeration period, also perhaps scale back on some maybe too > ambitious things we thought we could feasibly complete so we can > properly refrigerate. Thoughts? What’s the state of the dev branch > just now? > > Also, I will be flying to Utrecht to arrive for DH2019 on 6 July. > > Best, > Elisa > > Sent from my iPhone > _______________________________________________ > 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 > > > _______________________________________________ > 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 >
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ 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
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre
That worked. I was down to the three warnings from the tei_jtei.tei file, and I've now committed a fix for those. Cheers, Martin On 2019-07-02 12:20 p.m., Martin Holmes wrote:
Ah, right. I've installed it and kicked off a fresh build.
Cheers, Martin
On 2019-07-02 10:38 a.m., Hugh Cayless wrote:
I *think* if you just add the "ant-optional" package, the catalog resolution will just start to work. That's what Peter found when working with the Docker-based version of Jenkins.
On Tue, Jul 2, 2019 at 12:54 PM Martin Holmes <mholmes@uvic.ca <mailto:mholmes@uvic.ca>> wrote:
Jenkins2 is stumbling on the 429 errors coming from the tei-c server. If there's an update I need to do to Jenkins that isn't part of the repo itself, please let me know the details. Luis is looking at the question of whether he wants to allow lots of requests for the same files to come from the same server; I don't think he's keen, so the 429's might persist. They'll also presumably afflict OxGarage at some point.
Cheers, Martin
On 2019-07-02 6:55 a.m., Hugh Cayless wrote: > The dev branch is basically ok now, I think. There's one warning being > triggered on the JTEI exemplar, and I'm not sure whether that's a real > warning or one that should be ignored. Jenkins is happy, but Jenkins2 > (which hasn't been updated yet) is not. Given that the build was only > fixed last night, I'd be sympathetic to compressing or pushing back the > release timeframe. The real question in my mind is whether we ought to > delay the release... > > Hugh > > On Tue, Jul 2, 2019 at 9:43 AM Elisa Beshero-Bondar <ebbondar@gmail.com <mailto:ebbondar@gmail.com> > <mailto:ebbondar@gmail.com <mailto:ebbondar@gmail.com>>> wrote: > > Dear Councillors, > My calendar tells me we have entered the Refrigeration period > leading to the Freeze scheduled for 9 July next week. I have seen > that Refrigeration is often, ironically, a moment of heated work as > we try to resolve big issues and introduce something we care about > for the next release. I am trying that now with the long overdue > Measurement code (unitDecl, unitDef, etc), which really ought to be > coming out. I see intense activity with uniHan right now and wonder > if that too is targeted for this release? > > Here are some timing issues and updates. I have communicated with my > original release tech partner, Vanessa, and we agreed that, given > the lack of time she has had lately to work with us and concentrate > on the TEI, that it is best she defer being a release tech until > another time. As I see it, too, I expect this release to be > challenging—I am expecting the unexpected—because of all the server > issues recently and because the dev branch is still unstable with > all the unwanted excitement over the simplePrint ODD. Vanessa asked > me to convey her sincere apologies to Council for her absences and > lack of time. I hope after the season of deep preoccupation and > sadness that she will rejoin us with all the energy I know she has, > but now is not the moment. > > I am thankful to Magdalena for volunteering to host me near Warsaw > after the DH2019 conference next week, and she agreed that the two > of us will be the release techs. As we look at prepping this next > release, timing now really depends on both of us. I’m visiting her > from 13-20 July—and I think Magdalena has her own travel plans > starting (Saturday) 20 July. I think we’re safest if things go wrong > to make sure we do the release in the middle of that week. > > But it sounds like we’re still heatedly coding toward this release, > so I’d like to take stock of what we can complete just now—and reset > the Refrigeration period, also perhaps scale back on some maybe too > ambitious things we thought we could feasibly complete so we can > properly refrigerate. Thoughts? What’s the state of the dev branch > just now? > > Also, I will be flying to Utrecht to arrive for DH2019 on 6 July. > > Best, > Elisa > > Sent from my iPhone > _______________________________________________ > 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 > > > _______________________________________________ > 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 >
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ 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
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre
Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls #1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do! #1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review. #1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/ #1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“ Best Peter
Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM>:
My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Dear all, As Elisa noticed, I also understand the Refrigeration period as an intensive work phase where we try to resolve pending issues until we freeze.
I think we’re safest if things go wrong to make sure we do the release in the middle of that week.< Elisa and Magdalena, our original plan was to do the release on July 16. Is this still the plan?
Luis is currently looking at the parts of the release process where the TEI server is involved (step 12 in TCW22 - http://teic.github.io/CETEIcean/TCW22.html) to make sure that everything will work on the release day. He will provide us with information about possible changes within the next days. @pull requests - thanks Peter for the summary Agreed, our priority should be #1892 Measurement. #1901 uniHan: The intense work on uniHan is probably related with an email that I have sent to Duncan where I informed him about the release date. I think it would be great to integrate this in the release if Council thinks that this is possible. Here is the list with the currently open issues attached to the 3.6.0 milestone. https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+3..... I don't think we will complete all of these in time for the release. Can we remove the Release Blocker flag from https://github.com/TEIC/TEI/issues/1853? Best, Martina -----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces@lists.tei-c.org> Im Auftrag von Peter Stadler Gesendet: Mittwoch, 03. Juli 2019 08:40 An: Elisa Beshero-Bondar <ebbondar@GMAIL.COM> Cc: tei-council@lists.tei-c.org Betreff: Re: [Tei-council] Condensing (or compressing) Refrigeration? Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls #1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do! #1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review. #1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/ #1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“ Best Peter
Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM>:
My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
Hi Martina and all-- July 16 still looks okay to me as release day, and if completing an issue requires we need to move it forward a day or two, we should be okay, too. Probably the crucial question to ask is, will that day be good for Peter and Martin watching the Jenkins servers and others who can help us deal with crises? I've got some key access questions for you that I'll send off list. Cheers, Elisa On Wed, Jul 3, 2019 at 9:22 AM Scholger, Martina ( martina.scholger@uni-graz.at) <martina.scholger@uni-graz.at> wrote:
Dear all,
As Elisa noticed, I also understand the Refrigeration period as an intensive work phase where we try to resolve pending issues until we freeze.
I think we’re safest if things go wrong to make sure we do the release in the middle of that week.< Elisa and Magdalena, our original plan was to do the release on July 16. Is this still the plan?
Luis is currently looking at the parts of the release process where the TEI server is involved (step 12 in TCW22 - http://teic.github.io/CETEIcean/TCW22.html) to make sure that everything will work on the release day. He will provide us with information about possible changes within the next days.
@pull requests - thanks Peter for the summary
Agreed, our priority should be #1892 Measurement.
#1901 uniHan: The intense work on uniHan is probably related with an email that I have sent to Duncan where I informed him about the release date. I think it would be great to integrate this in the release if Council thinks that this is possible.
Here is the list with the currently open issues attached to the 3.6.0 milestone. https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+3..... I don't think we will complete all of these in time for the release. Can we remove the Release Blocker flag from https://github.com/TEIC/TEI/issues/1853?
Best, Martina
-----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces@lists.tei-c.org> Im Auftrag von Peter Stadler Gesendet: Mittwoch, 03. Juli 2019 08:40 An: Elisa Beshero-Bondar <ebbondar@GMAIL.COM> Cc: tei-council@lists.tei-c.org Betreff: Re: [Tei-council] Condensing (or compressing) Refrigeration?
Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls
#1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do!
#1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review.
#1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/
#1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“
Best Peter
Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM :
My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu <ebb8@pitt.edu> Development site: http://newtfire.org
I'll be on vacation the 16th. But if that's definitely the day, and I'm needed, I can make a point of keeping the morning at least clear and stay home that day to be on duty. Cheers, Martin On 2019-07-03 6:43 a.m., Elisa Beshero-Bondar wrote:
Hi Martina and all-- July 16 still looks okay to me as release day, and if completing an issue requires we need to move it forward a day or two, we should be okay, too. Probably the crucial question to ask is, will that day be good for Peter and Martin watching the Jenkins servers and others who can help us deal with crises? I've got some key access questions for you that I'll send off list.
Cheers, Elisa
On Wed, Jul 3, 2019 at 9:22 AM Scholger, Martina (martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>) <martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>> wrote:
Dear all,
As Elisa noticed, I also understand the Refrigeration period as an intensive work phase where we try to resolve pending issues until we freeze.
>I think we’re safest if things go wrong to make sure we do the release in the middle of that week.< Elisa and Magdalena, our original plan was to do the release on July 16. Is this still the plan?
Luis is currently looking at the parts of the release process where the TEI server is involved (step 12 in TCW22 - http://teic.github.io/CETEIcean/TCW22.html) to make sure that everything will work on the release day. He will provide us with information about possible changes within the next days.
@pull requests - thanks Peter for the summary
Agreed, our priority should be #1892 Measurement.
#1901 uniHan: The intense work on uniHan is probably related with an email that I have sent to Duncan where I informed him about the release date. I think it would be great to integrate this in the release if Council thinks that this is possible.
Here is the list with the currently open issues attached to the 3.6.0 milestone. https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+3..... I don't think we will complete all of these in time for the release. Can we remove the Release Blocker flag from https://github.com/TEIC/TEI/issues/1853?
Best, Martina
-----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces@lists.tei-c.org <mailto:tei-council-bounces@lists.tei-c.org>> Im Auftrag von Peter Stadler Gesendet: Mittwoch, 03. Juli 2019 08:40 An: Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>> Cc: tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> Betreff: Re: [Tei-council] Condensing (or compressing) Refrigeration?
Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls
#1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do!
#1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review.
#1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/
#1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“
Best Peter
> Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>>: > > My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu <mailto:ebb8@pitt.edu> Development site: http://newtfire.org <http://newtfire.org/>
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre
Martin-- I don't want us to interrupt your vacation! I do want to keep this somewhere in the middle of that week before Saturday July 20, when Magdalena and I part ways (she's heading off on a trip, and I'm going to Manchester). Is there a better day in that week for you? Elisa On Wed, Jul 3, 2019 at 2:53 PM Martin Holmes <mholmes@uvic.ca> wrote:
I'll be on vacation the 16th. But if that's definitely the day, and I'm needed, I can make a point of keeping the morning at least clear and stay home that day to be on duty.
Cheers, Martin
On 2019-07-03 6:43 a.m., Elisa Beshero-Bondar wrote:
Hi Martina and all-- July 16 still looks okay to me as release day, and if completing an issue requires we need to move it forward a day or two, we should be okay, too. Probably the crucial question to ask is, will that day be good for Peter and Martin watching the Jenkins servers and others who can help us deal with crises? I've got some key access questions for you that I'll send off list.
Cheers, Elisa
On Wed, Jul 3, 2019 at 9:22 AM Scholger, Martina (martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>) <martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>> wrote:
Dear all,
As Elisa noticed, I also understand the Refrigeration period as an intensive work phase where we try to resolve pending issues until we freeze.
>I think we’re safest if things go wrong to make sure we do the release in the middle of that week.< Elisa and Magdalena, our original plan was to do the release on July 16. Is this still the plan?
Luis is currently looking at the parts of the release process where the TEI server is involved (step 12 in TCW22 - http://teic.github.io/CETEIcean/TCW22.html) to make sure that everything will work on the release day. He will provide us with information about possible changes within the next days.
@pull requests - thanks Peter for the summary
Agreed, our priority should be #1892 Measurement.
#1901 uniHan: The intense work on uniHan is probably related with an email that I have sent to Duncan where I informed him about the release date. I think it would be great to integrate this in the release if Council thinks that this is possible.
Here is the list with the currently open issues attached to the 3.6.0 milestone.
https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+3.... .
I don't think we will complete all of these in time for the release. Can we remove the Release Blocker flag from https://github.com/TEIC/TEI/issues/1853?
Best, Martina
-----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces@lists.tei-c.org <mailto:tei-council-bounces@lists.tei-c.org>> Im Auftrag von Peter Stadler Gesendet: Mittwoch, 03. Juli 2019 08:40 An: Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>> Cc: tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> Betreff: Re: [Tei-council] Condensing (or compressing) Refrigeration?
Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls
#1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do!
#1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review.
#1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/
#1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“
Best Peter
> Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>>: > > My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu <mailto:ebb8@pitt.edu> Development site: http://newtfire.org <http://newtfire.org/>
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu <ebb8@pitt.edu> Development site: http://newtfire.org
I’ll be around between July 16 and 20 to help (but on vacation the week after). Best Peter
Am 03.07.2019 um 21:04 schrieb Elisa Beshero-Bondar <ebb8@pitt.edu>:
Martin-- I don't want us to interrupt your vacation! I do want to keep this somewhere in the middle of that week before Saturday July 20, when Magdalena and I part ways (she's heading off on a trip, and I'm going to Manchester). Is there a better day in that week for you?
Elisa
On Wed, Jul 3, 2019 at 2:53 PM Martin Holmes <mholmes@uvic.ca> wrote: I'll be on vacation the 16th. But if that's definitely the day, and I'm needed, I can make a point of keeping the morning at least clear and stay home that day to be on duty.
Cheers, Martin
On 2019-07-03 6:43 a.m., Elisa Beshero-Bondar wrote:
Hi Martina and all-- July 16 still looks okay to me as release day, and if completing an issue requires we need to move it forward a day or two, we should be okay, too. Probably the crucial question to ask is, will that day be good for Peter and Martin watching the Jenkins servers and others who can help us deal with crises? I've got some key access questions for you that I'll send off list.
Cheers, Elisa
On Wed, Jul 3, 2019 at 9:22 AM Scholger, Martina (martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>) <martina.scholger@uni-graz.at <mailto:martina.scholger@uni-graz.at>> wrote:
Dear all,
As Elisa noticed, I also understand the Refrigeration period as an intensive work phase where we try to resolve pending issues until we freeze.
>I think we’re safest if things go wrong to make sure we do the release in the middle of that week.< Elisa and Magdalena, our original plan was to do the release on July 16. Is this still the plan?
Luis is currently looking at the parts of the release process where the TEI server is involved (step 12 in TCW22 - http://teic.github.io/CETEIcean/TCW22.html) to make sure that everything will work on the release day. He will provide us with information about possible changes within the next days.
@pull requests - thanks Peter for the summary
Agreed, our priority should be #1892 Measurement.
#1901 uniHan: The intense work on uniHan is probably related with an email that I have sent to Duncan where I informed him about the release date. I think it would be great to integrate this in the release if Council thinks that this is possible.
Here is the list with the currently open issues attached to the 3.6.0 milestone. https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+3..... I don't think we will complete all of these in time for the release. Can we remove the Release Blocker flag from https://github.com/TEIC/TEI/issues/1853?
Best, Martina
-----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces@lists.tei-c.org <mailto:tei-council-bounces@lists.tei-c.org>> Im Auftrag von Peter Stadler Gesendet: Mittwoch, 03. Juli 2019 08:40 An: Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>> Cc: tei-council@lists.tei-c.org <mailto:tei-council@lists.tei-c.org> Betreff: Re: [Tei-council] Condensing (or compressing) Refrigeration?
Re what is to be included in the release, especially about the current pull requests, see https://github.com/TEIC/TEI/pulls
#1901 Unihan phase2: although the underlying ticket https://github.com/TEIC/TEI/issues/1805 is marked as green, this PR (taking some predecessors in account) was added only a few days ago. My instinct would be not to include it now because it’s too hot and I don’t see and Council member being really engaged in this currently? But I just added a Jenkins job for that branch so if anyone is willing to review that last minute, please do!
#1899 Build tweaks related to testing: This looks like a minor and uncontroversial issue but I don’t have time to review.
#1892 Measurement: this should really be our priority because it’s around for long(er). Elisa just fixed the last (technical) issues so the build succeeds but now we should take a careful look at the result at https://jenkins.tei-c.org/job/TEIP5-branch-measurement/
#1665 att.referring for <span>: quoting from the f2f minutes: "Syd and I [HC?] both think @referringMode is problematic, so the pull request can't be accepted as-is. There's also a dependency on the new standoff stuff in the examples, so perhaps discussion of this should be rolled into the standoff WG discussions. Needs a proposal, not a pull request. Also discussion in a separate Council call, and fold it into the standoff proposal.“
Best Peter
> Am 02.07.2019 um 15:42 schrieb Elisa Beshero-Bondar <ebbondar@GMAIL.COM <mailto:ebbondar@GMAIL.COM>>: > > My calendar tells me we have entered the Refrigeration period leading to the Freeze scheduled for 9 July next week. I have seen that Refrigeration is often, ironically, a moment of heated work as we try to resolve big issues and introduce something we care about for the next release. I am trying that now with the long overdue Measurement code (unitDecl, unitDef, etc), which really ought to be coming out. I see intense activity with uniHan right now and wonder if that too is targeted for this release?
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu <mailto:ebb8@pitt.edu> Development site: http://newtfire.org <http://newtfire.org/>
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
-- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu Development site: http://newtfire.org _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
participants (7)
-
Elisa Beshero-Bondar -
Elisa Beshero-Bondar -
Hugh Cayless -
Lou Burnard -
Martin Holmes -
Peter Stadler -
Scholger, Martina (martina.scholger＠uni-graz.at)