Fork me on GitHub
#cljs-dev
<
2019-01-03
>
dnolen22:01:52

might cut a release tomorrow, is there anything important I missed in the major/blocker list?

dnolen22:01:07

also did the website stuff get sorted?

borkdude22:01:47

@dnolen Not sure how important this one is, but I haven’t been able to find the cause yet: https://dev.clojure.org/jira/browse/CLJS-3023 Note that seq, rest, etc. have no problems, not sure what’s so specific about next.

dnolen22:01:24

it doesn't seem that important

dnolen22:01:29

instrumenting core is just low priority

borkdude22:01:01

It may have to do with apply using next a lot, and apply had the same problem, so let’s put it in that category for now

borkdude22:01:12

put the priority to minor now

mfikes22:01:15

I don't see any missing blockers, apart from CLJS-3030

borkdude22:01:58

I think I have a fix for the CLJS-3023 now though 🙂

mfikes23:01:13

Draft news release is a little thin at the moment; I’ll take a look at what landed this cycle and write some copy https://github.com/clojure/clojurescript-site/blob/news-next/content/news/2019-01-04-release.adoc

Alex Miller (Clojure team)23:01:29

Remember to poke me when you need the site built