In light of new maintenance policy...

[joenmoreno]

Is there going to be an official Spring 2.5.6 maintenance release to the community (with the usual tagging, binary downloads, maven repository release, etc.)? Or, is 2.5.5 the last one for the 2.5.x branch as far as the community (non-enterprise subscribers) is concerned?

I have already asked this question on a different thread but I have not received any official replies from anyone at SpringSource. I even sent an email to SpringSource directly (SpringSource.com -> Contact Us -> General Inquiries) and I have not received any answer yet.

[Paul Newport]

Is there going to be an official Spring 2.5.6 maintenance release to the community (with the usual tagging, binary downloads, maven repository release, etc.)? Or, is 2.5.5 the last one for the 2.5.x branch as far as the community (non-enterprise subscribers) is concerned?

I have already asked this question on a different thread but I have not received any official replies from anyone at SpringSource. I even sent an email to SpringSource directly (SpringSource.com -> Contact Us -> General Inquiries) and I have not received any answer yet.

My guess is the current answer is "no one knows", and that there is probably a serious amount of internal debate going on about it. My own opinion is that if they really want to go ahead with this strategy, it should be for new releases only (like Spring 3, Webflow 2.1).

Not that I agree with doing it anyway, as there is a serious flaw in the argument from Rod when he says:

"It only affects those who are unwilling to go near source code, or update to the latest version."

Well apart from the whole tagged/untagged trunk debate that makes it tricky to build from the source, it's pretty difficult to update to Spring 3 at the moment, as it's not out yet. There is a big point being made by SS about it beng onerous to support versions prior to the current release, and therefore they need to get people to pay for that, when the reality of the situation is that they want people to pay for maintenance releases of the current release, after 3 months.

I think it's fair enough to say "3 months after Spring 3 has come out, you'll have to pay for new releases of Spring 2.5.x if you want them, because the it costs too much to maintain old releases", but, following this line of reasoning, the charging for maintenance releases of Spring 2.5.x at the moment doesn't make sense, as Spring 3 isn't out yet.

So, to quote this again "It only affects those who are unwilling to go near source code, or update to the latest version." well, actually it does affect developers when there is no latest version to upgrade to.

[joenmoreno]

Wow. Still no word from SpringSource about this question? I guess you're right, Paul. At least from the Spring-core team, no one knows from what the answer is (regarding 2.5.6). I posted a the same question to the Spring-Batch forum (about Spring-Batch 1.1.3) and in less than an hour, somebody from that team gave a very precise answer. It's been 5 days since I posted my question and still no answer from the Spring-core guys.

[PascalAlberty]

I have the same question.

I "contribute" to this release by reporting some bugs and I'm working in dev with a snapshot and to finalize my own release I would like to get an official 2.5.6 release.

This one is postponed since several weeks (months ?), was plannified BEFORE the new maintenance release announce and I really waiting for it !

Please, SpringSource, tell us if you will release it to the world ... we have to know !

Thanks

[joenmoreno]

Why isn't there a straight answer? Is this not a simple question with a simple yes or no answer?

[kantorn]

Wonder if there is a silent "king-of-the-hill"-struggle in SS now... considering they got that new inverstor/market/business guy.....
Maybe that's why there aren't any answers. Funny, I thought that "money talks" was valid everywhere... but alas, not here.

[adam.fitzgerald]

Hi Joe,

I totally understand your frustration and the comments that have appeared in this thread. We don't want people to feel like we are keeping them in the dark but we also want to make sure we communicate to the community with a single voice that is definitive. We will be issuing a response that should address your concerns very soon.

Thanks for your patience.

Adam FitzGerald
SpringSource

[Grzegorz Grzybek]

Maybe this is the answer for us all after being kept in uncertainty for soooo long:

sourceforge.net/project/showfiles.php?group_id=73357&package_id=270072&rel ease_id=630203

springframework.org/taxonomy/term/4

(sorry for broken link - this is my first post )

best wishes for the entire Spring Community!!

[PascalAlberty]

Hi Joe,

I totally understand your frustration and the comments that have appeared in this thread. We don't want people to feel like we are keeping them in the dark but we also want to make sure we communicate to the community with a single voice that is definitive. We will be issuing a response that should address your concerns very soon.

Thanks for your patience.

Adam FitzGerald
SpringSource

Thanks adam for your answer.
That's all we wanted at short term ... at least an answer.

[joenmoreno]

Hi Joe,

I totally understand your frustration and the comments that have appeared in this thread. We don't want people to feel like we are keeping them in the dark but we also want to make sure we communicate to the community with a single voice that is definitive. We will be issuing a response that should address your concerns very soon.

Thanks for your patience.

Adam FitzGerald
SpringSource

Thanks Adam. It's been 5 days since your reply. 11 days since I first posted my question. Still no word about Spring Core 2.5.6. I have noticed that Spring Security 2.0.4 was released, and that's good. But that's not what I was asking. Should the community just assume that 2.5.6 will not be released to the community?