On Sat, Oct 1, 2011 at 10:16 PM, Tal Liron <tal.li...@gmail.com> wrote:
> And the issue for me now is concern about what will happen to all
> these contribs in the future if a core language feature changes, such as the
> dynamic Var issue in 1.3. If these contribs are not being built and shipped
> as part of Clojure, it seems risky to rely on them. Some might get upgraded,
> others might languish. What's lacking is any kind of statement of
> commitment. Instead, if I understand it correctly, we see the core Clojure
> project moving back from a commitment model to a more community-management
> model.
Actually I think you're in a better position now. The "new contrib"
libraries are all actively maintained and are expected to be
compatible with both Clojure 1.2.x and 1.3.0. I'm also hearing a
possibility that a "ready-to-go" download of updated contrib libraries
will be provided. That seems to address both of your concerns.
> I'm not necessarily arguing for a move back to the monolith that existed up
> to Clojure 1.2, but for a standard lib *distribution* with a test suite and
> a Clojure stamp of approval.
That's pretty much what "new contrib" is: they have active
maintainers, they have automated builds - with matrix tests against
Clojure 1.2.0, 1.2.1 and 1.3.0 on a variety of JDKs - they have
specific JIRA projects for logging bugs and requesting enhancements,
they have a documented process for maintenance. To become a "new
contrib" library, the project actually does need some level of
Clojure/core approval and involvement.
> example, the new dynamic Var breakage in Clojure could have been solved with
> an optional switch per namespace, requiring explicit enabling for now, and
But it can be solved by adding ^{:dynamic true} which makes it
compatible with both Clojure 1.2.x and 1.3.0. That's how 3rd party
libraries are solving this problem and being compatible with both
versions.
> will try to find time to go back to some of my old code, gather the
> workarounds I found for bugs -- a few in the JSON and in SQL-now-called-JDBC
> contribs -- and find a way to turn them into patches.
That would be cool - thank you. Have a read over the
http://clojure.org/contributing guidelines and the
http://clojure.org/patches process.
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
Railo Technologies, Inc. -- http://www.getrailo.com/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)
--
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
