Clojure 1.1 Release

Clojure 1.1 is now out:

http://clojure.googlecode.com/files/clojure-1.1.0.zip

It contains several new features and many bug fixes and small enhancements. Many people contributed ideas, patches, docs, testing, feedback etc to this release - it truly was a community effort.

http://www.assembla.com/spaces/clojure/tickets?milestone_id=93750&tickets_report_id=5

See the changes file for more details on the new features:

http://github.com/richhickey/clojure/blob/1.1.x/changes.txt

Many users have been running this code for a while now from the git repository, so I hope it continues the tradition of stability.

Without diminishing the efforts of any others, I'd like to call attention to the following:

Chris Houser has been helping me with patch commits and management of the Google Group. His efforts are invaluable to my staying focused on core issues.

Christophe Grand got his head around the transient mechanism and implemented it for several of the data structures, in addition to pursuing some of my more speculative ideas (with great success). This was a big help to me.

Tom Faulhaber has done a terrific job moving the API docs to a much better automated system hosted in the github repo:

http://richhickey.github.com/clojure/

To them, and everyone involved in the project - many thanks!

Rich

Clojure is Two!

It's hard to believe that another year has passed since I first released Clojure, now 2 years ago!

As with the first year, it's been a thrilling ride, with phenomenal growth. Some highlights (in no particular order, and omitting much, I'm sure):

• The release of Clojure 1.0, and many happy users of this stable version

• New features slated for 1.1
• Chunked seqs
• Transients
• test in core
• many fixes and enhancements

• New features underway for post 1.1
• Clojure-in-Clojure
• Parallel algorithms based upon latest ForkJoin

• We moved to Git and Assembla

• Stu Halloway's terrific book, and more books on the way
• Peepcode's screencast

• A viable CLR port, thanks to David Miller

• Many tutorials and blogs

• Lots of libraries, some with their own user groups
• Great growth in contrib
• Ever improving tools and IDE support

• At least five-fold increase in users and contributors (22,000+ messages from 2600+ list members, 90+ registered contributors)

• Talks I've given at ILC, QCon, JavaOne, Microsoft, JVM Language Summit, JAOO
• Many talks about Clojure given by others

• Clojure user groups springing up around the world
• Success stories from real-world applications
• Upcoming courses

It is clear that Clojure is taking off, and I attribute that to the fantastic community that has sprung up around it. Everyone continues to be supportive and friendly, and that matters quite a bit to newcomers who need help. It was great to hop on the #clojure irc this morning to find old hands chouser, cgrand and 170 others chatting away.

It takes much more than just the core language to make a language successful, and I want to thank everyone for your continued effort, support, suggestions, donations and patches. You are what makes Clojure great - find some cake and celebrate!

Rich

Clojure 1.0

After a sustained period of API stability and minimal bug reports, I'm happy to announce the release of Clojure 1.0!

http://clojure.googlecode.com/files/clojure_1.0.0.zip

Numbered releases will enable people to consume a stable version of Clojure and move to bugfix-only incremental versions while preserving API stability, and to consume libraries designed to work with specific versions. Providing the bugfix-only revisions depends upon the community to submit patches for the release branch as well as the trunk.

Clojure represents several years of effort on my part, but has also been shaped profoundly by the community in the 18 months since its release to the public. I can't thank everyone enough for your contributions of ideas, bug reports, suggestions, tests, tools, documentation and code - patches and enhancements. Clojure wouldn't be where it is today without its community and all of your efforts.

Of course, there is more to do. Many good ideas have been suggested in the discussions preceding this release that were best put off for 1.1. Now with the release we can pursue them, and many others:

http://clojure.org/todo

I want to give special thanks to those who have made donations - they really help! I did the core work on Clojure during a self-funded sabbatical that has run its course (i.e. through my savings :) - donations help fund the future.

Clojure 1.0 is a milestone of achievement, but it also represents a beginning. With 1.0, Stuart's book, the burgeoning set of libraries in and outside of contrib, and the large, friendly community, Clojure is poised to enter a period of increased adoption and application in many domains.

Here's to the future!

Rich