Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <48DB9EF1.8040302@apache.org>
Date: Thu, 25 Sep 2008 16:23:45 +0200
From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= <reinhard@apache.org>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: New Spring Maintenance policy
References: <48D7ED61.1020109@agssa.net> <48D9531F.3070104@gmx.de>
 <cc159a4a0809231343r6dad229em5eeb582e92217efc@mail.gmail.com>
 <48D959DD.5070307@gmx.de> <48D966E6.6090409@apache.org>
 <48D9E532.7040904@gmx.de> <48D9F59D.7000700@acrys.com>
In-Reply-To: <48D9F59D.7000700@acrys.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Rainer Pruy wrote:
> 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.

Thanks Rainer, that's more or less the same that I wanted to say. Maybe
SpringSource can be convinced to change their policy into this direction.

WDOT, would a petition help for that purpose?

-- 
Reinhard P�tz                           Managing Director, {Indoqa} GmbH
                         http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard@apache.org
________________________________________________________________________