A final round of buster updates for the Clojure team

[Alex Miller]

FYI on the perf regression fix for CLJ-2484, that patch is self-contained
and should apply cleanly to 1.10.0 if you wanted to do so. As of right now,
I do not expect to make any further changes wrt that issue in 1.10.1.

I'm hopeful that we will be able to release 1.10.1 without many more
updates (I do have one more queued up, but we will probably go RC after
that). I think 2-4 week expectation is the right ballpark timing for 1.10.1
if that is useful in making decisions.

Thanks for your work as always!
Alex

On Fri, Apr 19, 2019 at 9:26 AM Elana Hashman <ehashman at debian.org> wrote:

> Greetings programs!!
>
> Clojure is looking good for the buster release. We will be releasing
> with:
>
> - Clojure 1.10.0
> - Leiningen 2.9.0
> - Various supporting libraries and dependencies
>
> Additionally, I have successfully gotten clojure1.8 removed from
> testing, so we won't have to maintain multiple versions of Clojure in
> buster. Huzzah!
>
> What's next, if anything?
>
> Rob has pointed out that Clojure 1.10 has experienced a performance
> regression on JDK11, which seems to be getting patched in the 1.10.1
> release. However, that release is not yet available; currently only the
> preview build 1.10.1-beta2 is out. It is possible (likely?) that 1.10.1
> will not be released in time for buster.
>
> Here is some of our IRC banter on the subject for the record:
>
> 13:49 < rlb> ehashman: fwiw, looks like they maybe they did fix it.
> Invoking
>              1.10.1-beta2 clojure.main via a lein dummy app uberjar:
> 13:49 < rlb> $ cljr10
> 13:49 < rlb> Clojure 1.10.1-beta2
> 13:49 < rlb> user=>
> 13:49 < rlb>
> 13:49 < rlb> $ time cljr10 -e ''
> 13:49 < rlb> real    0m0.476s
> 13:49 < rlb> user    0m0.905s
> 13:50 < rlb> sys     0m0.089s
> 13:50 < rlb>
> 13:50 < rlb> For the current debian 1.10 it's 1.8s.
> 15:16 < ehashman> I think this is the perf regression:
>                   https://dev.clojure.org/jira/browse/CLJ-2484
> 15:18 < ehashman> (I'm looking at
>
> https://clojure.org/community/devchangelog#_release_1_10_1 )
>
> I think it is likely that we will *not* be able to take the patch for
> buster, but wanted to let the team know. If it was possible, this
> performance regression fix would be the last Clojure change targeted for
> buster, assuming the upstream release comes out on a schedule that works
> for the release team. I have no idea when 1.10.1 is coming out, but
> based on previous release schedules, since a release candidate isn't
> even available yet, I think it will be over a month.
>
> I do not want to try cherry-picking the performance fix while ignoring
> the rest of the upstream changes---while the patch is available on the
> JIRA I linked above, I don't know if it will apply cleanly to 1.10.0 and
> it's quite involved (>100 lines) so I don't want to accidentally
> introduce a regression or incompatibility with upstream.
>
>
> Until next time,
>
> - e
> _______________________________________________
> Pkg-clojure-maintainers mailing list
> Pkg-clojure-maintainers at alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-clojure-maintainers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-clojure-maintainers/attachments/20190419/775e1282/attachment-0001.html>