We've been using it on our development branch without a hitch since Dec 2.

On Thu, Dec 10, 2015 at 2:32 AM Michael Blume <blume.m...@gmail.com> wrote:

> No issues here.
>
> On Tue, Dec 8, 2015 at 5:39 PM James Elliott <brunch...@gmail.com> wrote:
>
>> I’ve been working with it for a few days and have seen no issues yet.
>>
>>
>> On Wednesday, December 2, 2015 at 10:03:31 AM UTC-6, Alex Miller wrote:
>>
>>> Clojure 1.8.0-RC3 is now available. *This build is a "release
>>> candidate"!* We would appreciate any and all testing you can do on your
>>> own libraries or internal projects to find problems.
>>>
>>> Try it via
>>>
>>>    - Download:
>>>    https://repo1.maven.org/maven2/org/clojure/clojure/1.8.0-RC3
>>>    - Leiningen: [org.clojure/clojure "1.8.0-RC3"]
>>>
>>> Below are the changes since 1.8.0-RC2. See the full 1.8 change log here:
>>> https://github.com/clojure/clojure/blob/master/changes.md.
>>>
>>>    - CLJ-1845 <http://dev.clojure.org/jira/browse/CLJ-1845> / CLJ-1851
>>>    <http://dev.clojure.org/jira/browse/CLJ-1851> New ^:redef to mark
>>>    vars that should not be direct linked
>>>       - The metadata ^:redef can be used to mark function vars that
>>>       should not be direct linked
>>>       - clojure.core/load was previously marked with ^:dynamic for this
>>>       purpose, but is now marked ^:redef
>>>    - CLJ-1856 <http://dev.clojure.org/jira/browse/CLJ-1856> Direct
>>>    linking breaks clojure.test location reporting for failures
>>>    - CLJ-1854 <http://dev.clojure.org/jira/browse/CLJ-1854> Set line
>>>    number in bytecode prior to invokeStatic call
>>>    - CLJ-1853 <http://dev.clojure.org/jira/browse/CLJ-1853> In socket
>>>    server, require the ns of the accept-fn before resolving it
>>>
>>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clojure@googlegroups.com
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to