This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-19
Channels
- # adventofcode (82)
- # beginners (70)
- # boot (34)
- # boot-dev (13)
- # cider (45)
- # clara (4)
- # cljs-dev (3)
- # cljsrn (2)
- # clojure (91)
- # clojure-art (8)
- # clojure-czech (1)
- # clojure-dusseldorf (3)
- # clojure-france (11)
- # clojure-germany (1)
- # clojure-greece (39)
- # clojure-hamburg (1)
- # clojure-italy (24)
- # clojure-norway (2)
- # clojure-spec (7)
- # clojure-uk (31)
- # clojurescript (56)
- # core-async (7)
- # cursive (8)
- # data-science (10)
- # datomic (41)
- # duct (7)
- # emacs (1)
- # events (1)
- # fulcro (83)
- # graphql (6)
- # klipse (1)
- # leiningen (28)
- # lumo (67)
- # off-topic (14)
- # om (9)
- # onyx (3)
- # perun (4)
- # re-frame (22)
- # reagent (11)
- # ring-swagger (2)
- # rum (1)
- # specter (46)
- # sql (13)
- # uncomplicate (17)
- # unrepl (114)
suggestions for a SNAPSHOT version number with the Pomegranate change above? 🔺 2.8.0-SNAPSHOT 🔸 2.7.3-SNAPSHOT
^ can we get a consensus on how boot should handle symlinks?
Probably 2.8.0 is better
, I even think we should get a 3
just to make clear that we bumped pomegranade
I see why we’d go straight for 3.0.0 but at the same time it’s not a breaking change really is it? I guess at some point we should come up with some more well-defined versioning scheme
You are probably right, mine is more like defensive programming I guess 😄
Well, defensive seems good. We just need something that we can consistently follow. If we decide fresh everytime that probably won’t be very consistent 😛
FWIW I don’t have any strong feelings about going straight to 3.0.0
, if anyone else here thinks we should do that, make yourself heard 🙂
Agree totally with you first point, I feel that bumping the dep resolution is a strong motivator...but then let's agree of what it is and what not...I guess 😄
3.0.0 suggests some pretty major changes -- so I think 2.8.0 strikes the right balance.
@flyboarder I have never run into that, how to test it?
@richiardiandrea im no longer running into this issue, however if you place a symlink within a boot/tmpdir!
and add-resource
with that directory you should see the issue, basically the symlink was being turned into a corrupt file
but this might be resolved already
I see why we’d go straight for 3.0.0 but at the same time it’s not a breaking change really is it? I guess at some point we should come up with some more well-defined versioning scheme
You are probably right, mine is more like defensive programming I guess 😄
@alandipert hey, can you add me to the boot
group on Clojars? 🙂
FWIW I don’t have any strong feelings about going straight to 3.0.0
, if anyone else here thinks we should do that, make yourself heard 🙂
3.0.0 suggests some pretty major changes -- so I think 2.8.0 strikes the right balance.