Comments on: Some thoughts on the new SpringSource maintenance policy http://springinpractice.com/2008/10/01/some-thoughts-on-the-new-springsource-maintenance-policy/ Willie Wheeler's Spring blog Thu, 17 May 2012 13:28:20 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: williewheeler http://springinpractice.com/2008/10/01/some-thoughts-on-the-new-springsource-maintenance-policy/#comment-10 williewheeler Thu, 02 Oct 2008 07:44:16 +0000 http://springinpractice.wordpress.com/?p=109#comment-10 Yeah, I read the long and heated discussion over at TSS and I can see that Rod is trying to help people understand the argument that this move actually benefits the community. Obviously not everybody will accept that--there's clearly a tradeoff being made here (community loses some of the bugfix releases but now SpringSource is in a better place to fund ongoing development of new features)--but at least people should try to understand the argument. At any rate, I support the change; I just hope that you guys are able to help people better understand both the nature of the change and the reasoning behind it. I can see that you're trying. :-) Yeah, I read the long and heated discussion over at TSS and I can see that Rod is trying to help people understand the argument that this move actually benefits the community. Obviously not everybody will accept that–there’s clearly a tradeoff being made here (community loses some of the bugfix releases but now SpringSource is in a better place to fund ongoing development of new features)–but at least people should try to understand the argument.

At any rate, I support the change; I just hope that you guys are able to help people better understand both the nature of the change and the reasoning behind it. I can see that you’re trying. :-)

]]> By: Adam FitzGerald http://springinpractice.com/2008/10/01/some-thoughts-on-the-new-springsource-maintenance-policy/#comment-9 Adam FitzGerald Thu, 02 Oct 2008 07:34:55 +0000 http://springinpractice.wordpress.com/?p=109#comment-9 Thanks for your thoughtful consideration of how the SpringSoure Maintenance Policy will affect you. I agree that the definition of major release is not clear in the news announcement. We tried to clear it up in the <a href="http://www.springsource.com/products/enterprise/maintenancepolicy/faq" rel="nofollow">FAQ</a> that was published shortly afterwards: <blockquote> <strong>What is the definition of a major release?</strong> A major release is defined as a release which incorporates major new functionality into the software. A major release is indicated by a change in either the first or second digit of the version number. Going from 2.5 to 3.0 or from 3.0 to 3.1 would be considered a major releases. </blockquote> All the vigorous discussion in the community has provoked lots of deep thinking at SpringSource. I know Rod is planning further clarification soon. Adam FitzGerald SpringSource Thanks for your thoughtful consideration of how the SpringSoure Maintenance Policy will affect you. I agree that the definition of major release is not clear in the news announcement. We tried to clear it up in the FAQ that was published shortly afterwards:

What is the definition of a major release?
A major release is defined as a release which incorporates major new functionality into the software. A major release is indicated by a change in either the first or second digit of the version number. Going from 2.5 to 3.0 or from 3.0 to 3.1 would be considered a major releases.

All the vigorous discussion in the community has provoked lots of deep thinking at SpringSource. I know Rod is planning further clarification soon.

Adam FitzGerald
SpringSource

]]>