Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ralph.goers@dslextreme.com
 designates 66.51.199.81 as permitted sender)
Message-ID: <4490183E.6060206@dslextreme.com>
Date: Wed, 14 Jun 2006 07:07:58 -0700
From: Ralph Goers <Ralph.Goers@dslextreme.com>
Reply-To: rgoers@apache.org
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: [2.2] Release?
References: <448E501B.80701@apache.org> <448F0936.8070304@apache.org>
 <448FEF80.1020800@apache.org> <448FF301.3010606@apache.org>
 <44900135.9010002@apache.org>
In-Reply-To: <44900135.9010002@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>
>> So this means we release some jars and the plugins? I think one
>> important goal of this
>> release should be to get feedback, so we should try to make the barrier
>> to test 2.2 as low as possible while puttint as less effort as possible
>> into it. I'm not sure if just releasing maven artifacts is enough here.
>
> Which kind of feedback do you want?
> I think we need feedback from people that migrate their projects to 
> C22. I don't believe it makes sense to use C22 without a Maven 2 based 
> build. And, as I said in many previous mails, a distribution that can 
> be compared to a C21 release has its only purpose in being a demo 
> application, nothing more.
I suspect that Carsten didn't understand what you were saying as this 
sentence, "I don't think that we should only provide Maven artifacts for 
our first release, nothing more." would lead one to believe that you do 
NOT want to ship anything regarding maven 2.
>
> So yes, I think that the named artifacts are enough for a first 
> release. Releasing forms, fop, javaflow, apples, batik, mail and 
> portal should be the next step so that more people can start to 
> experiment with a migration. During this phase we should fix their 
> samples too.
>
> Finally, we don't have to provide *one* release that contains all our 
> 50+ blocks anymore. Luckily we can release iterativly whenever 
> something is ready :-)
I have no problem with this release as a first step, but I'd hesitate to 
even call it 2.2M1.  OTOH, if I had an idea of what our subsequent 
milestones are this might make more sense to me.

Ralph