So we propose to publish a 2.13.8 release candidate by December 17, followed by a final 2.13.8 release no earlier than January 5. (Depending on how things go these dates might have to change, but even if they do, we’ll be sure not to intrude on the holidays.)
If you’re aware of anything you think ought to be considered a blocker for this release, please let us know, either by commenting on the appropriate ticket or PR, or by replying on this thread.
This time window is way too short to introduce regressions to the code base.
Maybe in the next cycle, you could announce a date for “regression freeze”, after which no new regressions will be permitted.
There is the PR about supplementary char support that just missed the previous cut-off, which was beaten by the previous PR about supplementary char support. It was so long ago, I don’t recall the details, but I do remember that it was when I learned about the cyclone operator. It closes four tickets not opened by me. Probably I had already exhausted Martijn’s good will in reviews.
Scala 3 is also not staffed for code review of low-priority contributions. That PR that was merged predicated on “seems clear the Scala 3 forward port will land”, it hasn’t yet.
It would indeed be really sad if this was not included, because the PR looks really good and I just wanted to confirm that all the different reports it closes are actually covered
Update on 2.13.8 progress: the community build found a collections regression. We have reverted the PR in question and will re-run the community build tonight. (We weren’t able to run it last night due to some trouble with our Jenkins, which Lukas has since resolved.)
We’re pushing the target rebuild date out to Monday, January 10, though. So if the holiday break prevented you from doing any testing, yet, well: here’s your chance!
FYI, I am now on sick leave because of covid. Nothing to worry about but I’m very tired. I will do my best to release Scala.js ASAP for 2.13.8, but there might be a longer delay than usual.
We already have the support for 2.13.7 in the recent SNAPSHOT. We are working on the full release now, but there was a couple of things we needed to fix beforehand. We should be able to finalize it tomorrow.