Chariot Training Classes

Training Courses

I run Chariot's training and mentoring services. We provide training in AngularJS, HTML5, Spring, Hibernate, Maven, Scala, and more.

Chariot Education Services

Technology

Chariot Emerging Tech

Learn about upcoming technologies and trends from my colleagues at Chariot Solutions.

Resources

Chariot Conferences

Podcasts

« Mono 2.0 Released | Main | Google Guice, First Look »
Wednesday
Oct082008

Updated SpringSource Distribution Policy

Note: I'm updating this article's title. Rod had noted it's not a licensing change, rather a distribution change. I made the change to my post text, but not the URL or the article title.

Read the updated SpringSource distribution decision on Rod Johnson's Blog Page. This is a change to a recent policy decision by SpringSource to provide updates for 3 months after a new major/minor release.

The change provides for releases of builds to the open source community until a new major/minor version is delivered. For example, the current 2.5.5 release would be revved to 2.5.6 (based on Rod's information) and once a 3.0 release is provided, the 2.5.x line would be provided but not updated (unless your organization is a SpringSource licensee under support contract).

This is a fair agreement, as open source teams can now continue building applications based on Spring and decide when they are ready to update to a newer version of the software, without worrying about purchasing support. Concordant with this change are upcoming licensing models for small business and systems integrators.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (2)

Thanks for the kind words. However, I did want to note that we never proposed a *licensing* change: merely a distribution change.

Rgds
Rod

October 8, 2008 | Unregistered CommenterRod Johnson

Thanks for the clarification, Rod. I changed from licensing to distribution in the text.

Ken

October 8, 2008 | Unregistered Commenterkrimple

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>