Fork me on GitHub
#clojure-dev
<
2015-10-13
>
alexmiller14:10:25

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.

bronsa19:10:36

@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

alexmiller19:10:09

the cool thing about releases is ... there's always another one

alexmiller19:10:31

beta means: "no more enhancements"

alexmiller19:10:40

rc means: "we think it's done"

bronsa20:10:10

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

alexmiller20:10:50

there will be more beta releases

bronsa20:10:50

I'm sure of that, I just don't understand what urged cutting a knowingly broken release

alexmiller20:10:20

this is a totally artificial distinction

alexmiller20:10:28

every release is knowingly broken

alexmiller20:10:59

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

alexmiller20:10:42

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

bronsa20:10:52

couldn't reversing the dl stuff for this release be considere then?

alexmiller20:10:10

yes, and that's rich's call

alexmiller20:10:00

while I know 1809 is an issue for some people, it is also not an issue for a very large percentage of users

bronsa20:10:48

@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

bronsa20:10:08

I think cljs users are quite a large percentage

alexmiller20:10:56

cljs users can use 1.7 - there is no reason anyone has to use the 1.8 alpha/betas

bronsa20:10:20

if nobody uses the alpha/betas how are we going to find regressions?

alexmiller20:10:13

I said no one has to use them, not that no one should use them

alexmiller20:10:44

if you look at the build box, you will notice that there are no projects broken by 1.8 beta1

bronsa20:10:11

(except for t.a.js, but that's not clojure's fault simple_smile )

alexmiller20:10:51

that was my point

cfleming21:10:06

Is CLJ-322 likely to get any love in 1.8?

ghadi21:10:15

Probably not due to beta cycle

alexmiller21:10:15

the only things still likely to get in are tickets in Screened or Screenable

bronsa21:10:04

@alexmiller: are the other tickets marked 1.8 going to be bumped to 1.9 then?

alexmiller21:10:56

afaik the ones currently in screenable or screened will stay in 1.8

alexmiller21:10:28

if you're talking about stuff in incomplete, most of those are waiting on something and will likely get moved

alexmiller21:10:44

but we have not talked about any of that yet, I'm just guessing

bronsa21:10:06

yeah I meant the tickets marked 1.8 that are neither screened nor screenable