Re: [Membership] Plone Version Support Policy: Call for Input

Previously Veda Williams wrote:
> I'm not sure that I'm the best person to speak here, but I don't even
> remember exactly when 3.0 came out, and drawing a line of a year feels
> awfully random to me. Version-based support sounds better to me, for
> security fixes only.
> 
> I think we need to have a methodology for determining if it's time to let a
> release fade into the mists:
> 
> 1) Is documentation for the current version up to date?
> 
> 2) Has plone.org managed to move to the new version?
> 
> 3) Has the volume of questions started leaning toward the newest version of
> Plone (80% at least)?
> 
> 4) Do we have the volunteer power to do minor security fixes to older
> versions?
> 
> 5) How long will it be before the next major release? (1 or 2 years is an
> awfully long time to wait, and what's the harm in doing small security fixes
> to an older version in that time frame?)

The problem is that none of these are predictable or measurable. And
predictability is very important: if someone is going to spend a lot of
money on a Plone site he will only do so if they know in advance how
long they can count on support.

Wichert.

-- 
Wichert Akkerman <[email protected]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

------------------------------------------------------------------------------