cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Pruy <Rainer.P...@Acrys.COM>
Subject Re: New Spring Maintenance policy
Date Wed, 24 Sep 2008 08:09:01 GMT

yes, all the wording is quite confusing.
The "statement" cited by Peter is trying to convince readers into believing "it will affect
only old releases",
but there nowhere is a guarantee put up that there will be a new release within the 3month
And the policy puts up that 3 month period per release without referring to later releases.

A clear statement along "only the most current release will receive maintenance efforts"
would have been much easier and clearer (and would get broader acceptance by the community).
That the whole thing was not put that way contributes to the impression that users should
be convinced into a support contract.


Joerg Heinicke schrieb:
> 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.
> Joerg

View raw message