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:
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.
On May 4, 9:46 am, AlamedaMike <amino.metr...@gmail.com> wrote:
|> Congratulations, Rich! And thanks for all your hard work. Having a
1.0
|> release out to help adoption in the workplace environments that we
|> need to get into.
Indeed, this is the case where I work. Having a stable version to
target will make it possible for me to develop projects on the clock.
> 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:
> 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.
This is a very cool! I have one suggestion: maybe we should update the
clojure website and add the announcement of 1.0 release. I know that
Rich has announce the news in the blog. However, most of the people
will just go to
http://clojure.org/. Therefore, I think that it is very important to
put the announcement on the main website. Any comment?
On May 4, 7:58 am, Rich Hickey <richhic...@gmail.com> wrote:
> 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:
> 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.
Congratulations, Rich! And thanks for all your hard work. Having a 1.0
release ought to help adoption in the workplace environments that we
need to get into.
On May 4, 9:51 am, "mchan...@uiuc.edu" <changming...@gmail.com> wrote:
> This is a very cool! I have one suggestion: maybe we should update the
> clojure website and add the announcement of 1.0 release. I know that
> Rich has announce the news in the blog. However, most of the people
> will just go tohttp://clojure.org/. Therefore, I think that it is very important to
> put the announcement on the main website. Any comment?
> 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:
> 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.
> 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:
> 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.
> 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:
> 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.
Wow, I really didn't expected this one! I also came to realize that
I've been using Clojure for a year now, the longest period of time
I've devoted to a single non-mainstream language. A million thanks!
Congratulations to Rich and all contributors.
On May 4, 8:58 am, Rich Hickey <richhic...@gmail.com> wrote:
> 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:
> 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.
I made a promise to myself long ago to really learn a Lisp. I've dabbled on and off but now Clojure is really motivating me to really learn - sane concurrency model and on the JVM so I have all sorts of libraries at my disposal and availability "everyone" what's not to love?
> 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:
> 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.
> 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:
> 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.
> > 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:
> > 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.
Thanks a lot and congrats to you and the Clojure community.
Finally I think I have found a practical Lisp I can devote myself to.
Hoping for great times ahead.
> 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:
> 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.
Congratulations!
I'm loving and enjoying Clojure programming.
Clojure is the most beautiful, practical and fun language I've ever seen.
Thank you very much for your great work!
> Congrats! I'm loving Clojure more all the time. Thank you for making
> the Lisp I've been waiting for all these years.
> Travis
> On May 4, 8:58 am, Rich Hickey <richhic...@gmail.com> wrote:
>> After a sustained period of API stability and minimal bugs reports,
>> I'm happy to announce the release of Clojure 1.0!
>> 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:
>> 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.
I've submitted the announcement to Slashdot. It's in the firehose
right now. If anyone has an account, you can go vote for the
submission and perhaps we can get it on the front page.
> Congratulations!
> I'm loving and enjoying Clojure programming.
> Clojure is the most beautiful, practical and fun language I've ever seen.
> Thank you very much for your great work!
> > Congrats! I'm loving Clojure more all the time. Thank you for making
> > the Lisp I've been waiting for all these years.
> > Travis
> > On May 4, 8:58 am, Rich Hickey <richhic...@gmail.com> wrote:
> >> After a sustained period of API stability and minimal bugs reports,
> >> I'm happy to announce the release of Clojure 1.0!
> >> 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:
> >> 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.