Re: [Tei-council] Condensing (or compressing) Refrigeration?

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