This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-13
Channels
- # admin-announcements (48)
- # alda (1)
- # aws (24)
- # beginners (4)
- # boot (103)
- # cider (69)
- # clojure (111)
- # clojure-art (5)
- # clojure-dev (35)
- # clojure-greece (2)
- # clojure-nl (3)
- # clojure-russia (1)
- # clojure-shanghai (1)
- # clojurescript (220)
- # clojurescript-ios (1)
- # clojurewerkz (3)
- # community-development (3)
- # core-logic (5)
- # cursive (5)
- # datomic (24)
- # devcards (21)
- # editors (3)
- # funcool (1)
- # hoplon (20)
- # ldnclj (47)
- # ldnproclodo (1)
- # liberator (1)
- # off-topic (7)
- # om (21)
- # onyx (36)
- # reagent (1)
- # ring-swagger (2)
- # spacemacs (38)
- # yada (17)
re the beta1 release, CLJ-1809 (and CLJ-1805) are known important things but Rich hasn't had time to look at them so we decided to release this beta without them. that stuff will probably be resolved in the next beta.
@alexmiller: not sure if that makes much sense tbh, I don't see much value in a first beta if it's known to break production code
the cool thing about releases is ... there's always another one
beta means: "no more enhancements"
rc means: "we think it's done"
beta releases have (and I'm sure you're well aware of this) always been particularly useful to find regressions, this isn't really possible given that we're shipping a severly bugged compiler
there will be more beta releases
I'm sure of that, I just don't understand what urged cutting a knowingly broken release
this is a totally artificial distinction
every release is knowingly broken
we had not shipped a release in a while and we wished to round off the set of enhancement related things in a beta1, so we did a release
every Clojure version I've been involved with had problems that were introduced in alpha/betas, persisted across multiple of them and were fixed by rc
yes, and that's rich's call
while I know 1809 is an issue for some people, it is also not an issue for a very large percentage of users
@alexmiller: this is the first time I see a clojure this broken get released as a beta, I remember betas dropping back to alpha version when severe bugs were noticed
cljs users can use 1.7 - there is no reason anyone has to use the 1.8 alpha/betas
I said no one has to use them, not that no one should use them
if you look at the build box, you will notice that there are no projects broken by 1.8 beta1
that was my point
the only things still likely to get in are tickets in Screened or Screenable
http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10383 or http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10374 that is
@alexmiller: are the other tickets marked 1.8 going to be bumped to 1.9 then?
afaik the ones currently in screenable or screened will stay in 1.8
if you're talking about stuff in incomplete, most of those are waiting on something and will likely get moved
but we have not talked about any of that yet, I'm just guessing
those are all (I think) in Incomplete http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10375