[Yanel-dev] [Fwd: Re: New Spring Maintenance policy]

[Michael Wechner]

this might also be of interest to us ...

-------- Original-Nachricht --------
Betreff: 	Re: New Spring Maintenance policy
Datum: 	Thu, 25 Sep 2008 11:19:29 +0200
Von: 	Sylvain Wallez <sylvain at apache.org>
Antwort an: 	dev at cocoon.apache.org
An: 	dev at cocoon.apache.org
Referenzen: 	<48D7ED61.1020109 at agssa.net> <48D9531F.3070104 at gmx.de> 
<cc159a4a0809231343r6dad229em5eeb582e92217efc at mail.gmail.com> 
<48D959DD.5070307 at gmx.de> <48D966E6.6090409 at apache.org> 
<48D9E532.7040904 at gmx.de> <48D9FBD6.10706 at apache.org> 
<48DA3D0E.4020405 at mobilebox.pl>



Leszek Gawron wrote:
> Sylvain Wallez wrote:
>> Joerg Heinicke wrote:
>>> On 24.09.2008 00:00, Sylvain Wallez wrote:
>>>
>>>> Yeah. I read this as "3 months after release n+1 is out, release n 
>>>> becomes closed source". I'm wondering how long it will take for 
>>>> forks to appear that will provide open source bug fixes to old 
>>>> releases.
>>>
>>> I don't think that's n+1 but n: "After a new major version of Spring 
>>> is released, community maintenance updates will be issued for three 
>>> months to address initial stability issues." They wouldn't talk 
>>> about "initial stability issues" anymore if it were n+1.
>>
>> Wow, that's even worse...
>
> That move is probably plain stupid. Rod Johnson states that the full 
> source tree will still be available - there will be simply no public 
> releases after 3 months and no svn tags to build that release 
> yourself. You will only be able to build snapshots (better said 
> internal releases) to address the issues you encounter.
>
> Yet again: plain stupid. Every open source project will have to track 
> it's spring version by its own. How will the project be able to report 
> issues if 99% of the world will be using snapshots?
>
> "My spring version r144554 shows some problem"? Clearly this is very 
> short sighted.

There's an easy way the OSS community can react to that: create an 
OpenSpring.org website that will provide "official open source 
maintenance releases" from well-known revisions of the SpringSource SCM.

That way, people will be able to use e.g. "openspring 2.4.8" which will 
actually be springsource r144554

> It is even more insulting to the comunity stating that it is too 
> costly for SpringSource to do 'mvn deploy' from time to time. It's 
> just a marketing version of "Buy a damn subscription!".
>
> There's an quick and easy way to force users to subscription: just 
> make major releases less frequent.
>
> If you haven't read on TSS: Although the prices are not publicly known 
> someone stated that yearly subscription is something about $16 000...

Ouch. Spring was born as a lightweight and open source alternative to 
big and costly J2EE containers. It's now as big and costly (and as 
bloated?) as a J2EE container...

Sylvain

-- 
Sylvain Wallez - http://bluxte.net