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.6.0%22+is%3Aopen. 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?