Clojure 1.3 compatibility.

[Nicolas Buduroi]

Hi everyone, I just wanted you to know that a 1.0.0-SNAPSHOT version
is available which use Clojure 1.3. Lobos will require 1.3 from now on
so you can always use 0.8 for projects running on 1.2. Big thanks to
James Reeves for figuring out the post-contrib transition.

The 1.0.0 version is coming, the next few weeks will be your last
chance to propose non-backward compatible changes to the API so don't
hesitate to fill issues on Github.

Finally, I'll might find more time to continue working on Lobos in the
coming weeks, hopefully next winter will be as productive than the
last.

[James Reeves]

On 15 October 2011 05:42, Nicolas Buduroi <nbud...@gmail.com> wrote:
> Hi everyone, I just wanted you to know that a 1.0.0-SNAPSHOT version
> is available which use Clojure 1.3. Lobos will require 1.3 from now on
> so you can always use 0.8 for projects running on 1.2. Big thanks to
> James Reeves for figuring out the post-contrib transition.

We don't actually need to choose between 1.2 and 1.3, because the
Clojure dependency chosen by the user overrides the Clojure dependency
chosen by Lobos.

For example, if I specify the following dependencies:

[[org.clojure/clojure "1.2.1"]
[lobos "1.0.0-SNAPSHOT"]]

Then when I run "lein deps", the following files are placed in my lib directory:

clojure-1.2.1.jar
lobos-1.0.0-20110809.143608-1.jar
java.jdbc-0.0.7.jar
tools.macro-0.1.1.jar

Even though Lobos depends on Clojure 1.3, I can still use it with 1.2,
so long as the Lobos source code remains backward compatible with 1.2
(which it is).

My feeling is that until Clojure 1.3 becomes the norm, we should seek
to remain backward-compatible with 1.2. This will allow both 1.2 users
and 1.3 users to use Lobos equally without problem.

- James