This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-15
Channels
- # aleph (1)
- # announcements (7)
- # beginners (6)
- # calva (24)
- # cider (18)
- # clj-otel (1)
- # clojars (8)
- # clojure (22)
- # clojure-dev (11)
- # clojure-europe (52)
- # clojure-finland (12)
- # clojure-nl (1)
- # clojure-norway (28)
- # clojure-uk (7)
- # clojured (1)
- # cursive (6)
- # datomic (1)
- # events (1)
- # humbleui (41)
- # hyperfiddle (75)
- # lsp (46)
- # malli (34)
- # matrix (1)
- # off-topic (16)
- # releases (1)
- # shadow-cljs (12)
- # squint (11)
- # timbre (1)
- # tools-deps (24)
Has the core team ever considered “nightly” releases? There’s not a ton of movement in core, but there’s more than gets released in alphas, and it might be helpful catching regressions
We can release snapshots from master now, we just rarely have need to do so. Generally we commit a set of patches just to do a release.
Is the SNAPSHOT build/deploy no longer run automatically like it used to every time there were commits to master?
(I have long had a :master
alias in my user deps.edn
to enable testing against the "nightly" builds -- and several of my OSS projects test against multiple Clojure versions including :master
)
It’s no longer automatic
It’s fairly rare that it’s different from last release
Usually we commit a bunch of patches, and then do a release
You're not committing to master outside of releases as much as you used to, it's true. Is that ever likely to change back? Just thinking I might as well remove :master
from my CI builds and just track :1.12
manually as each new release appears...
don't know
prediction is difficult, especially about the future
Heh, fair enough. Certainly, testing against :master
these days is a bit of a waste of time 🙂