Spring Alienating Users?

[Gregg Bolinger]

http://www.springsource.com/node/558

What I Get from that is that Spring community users (non commercial support paying folks) will only get maintenance releases of Spring after a SpringSource major version release. So we now have to live with all the bugs for months at a time.

Anyone else have a huge problem with this besides me?

[Joachim Rohde]

"After a new major version of Spring is released, community maintenance updates will be issued for three months to address initial stability issues.

From the quote I get that that community users will get maintenance releases up to 3 months after a major release. And I guess that within three months the version should be stable enough for production.
From this perspective I don't have a huge problem with that.

But what would be nice to know, is, 'what' is a new major version? Was the step from 2.0 to 2.5 already a major version? Or only the step from 1.0 to 2.0?

[Mark Spritzler]

Gregg you have a filled PM box.

Mark

[Gregg Bolinger]

Originally posted by Mark Spritzler:
Gregg you have a filled PM box.

Mark

Not anymore.

[Mark Spritzler]

While employees like me can't comment. It is even better still if the comment accurately came from a third party anyway.

http://www.jroller.com/habuma/entry/what_the_new_springsource_maintenance

Mark

[Gregg Bolinger]

Originally posted by Mark Spritzler:
While employees like me can't comment. It is even better still if the comment accurately came from a third party anyway.

http://www.jroller.com/habuma/entry/what_the_new_springsource_maintenance

Mark

Good to know. Thanks.

[Ulf Dittmer]

http://www.jroller.com/habuma/entry/what_the_new_springsource_maintenance

The part about not tagging the repository sounds nasty. Even if I find out that an important bug fix has been committed -and that's apparently not a given-, I have no guarantee that the top of the trunk which I'm about to check out doesn't contain loads of poorly tested, buggy code. That doesn't exactly inspire confidence.

[Gregg Bolinger]

I'm just going to let it ride for a bit. I've found an interesting, and believe it or not lighter, stack that I can swap out for what I am using Spring for. My usage of Spring is actually quite small. So I am not abandoning it completely until I read more into this and gain more knowledge about what is actually going to happen.

I understand building a commercial model around an open source project but it has to be handled correctly so that the community doesn't suffer. And I can't take too much from Mark only because he has vested interest in SpringSource succeeding. No offense, but I need more unbiased views into the whole thing.

So I'll just sit back and watch what happens for now.

[Mark Spritzler]

Originally posted by Gregg Bolinger:
I'm just going to let it ride for a bit. I've found an interesting, and believe it or not lighter, stack that I can swap out for what I am using Spring for. My usage of Spring is actually quite small. So I am not abandoning it completely until I read more into this and gain more knowledge about what is actually going to happen.

I understand building a commercial model around an open source project but it has to be handled correctly so that the community doesn't suffer. And I can't take too much from Mark only because he has vested interest in SpringSource succeeding. No offense, but I need more unbiased views into the whole thing.

So I'll just sit back and watch what happens for now.

I didn't give any opinion at all.

Mark

[Joachim Rohde]

For those who haven't read the blog of Rod Johnson the last days, should have a look at http://blog.springsource.com/2008/10/07/a-question-of-balance-tuning-the-maintenance-policy/ where Rod clears a few things out, regarding the release policy.