Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41DBC18D.5030700@upaya.co.uk>
Date: Wed, 05 Jan 2005 10:29:33 +0000
From: Upayavira <uv@upaya.co.uk>
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Using the standard Jaxp parser in Cocoon.java
References: <41DA73F5.8010201@anyware-tech.com> <41DA7C7E.4050007@apache.org>
    <41DA8C91.7020605@upaya.co.uk> <41DA920E.90204@apache.org>
    <41DAA8C6.1090004@upaya.co.uk> <41DAAB0D.5050301@apache.org>
    <41DAB039.5070008@apache.org>
 <33214.10.0.0.5.1104873376.squirrel@www.agssa.net>
 <41DB084E.7040409@upaya.co.uk> <41DB8F07.8010706@apache.org>
In-Reply-To: <41DB8F07.8010706@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:

> Upayavira wrote:
>
>> Antonio Gallardo wrote:
>>
>
>>>
>>> If 2.1 will work without this "feature" => please remove it. 
>>> Cleaning the
>>> house is good. ;-)
>>>  
>>>
>> As is leaving things alone so you don't take the risk of breaking 
>> things :-)
>>
> Exactly - and we should try to make sense out of our version numbers 
> especially wrt compatibility.

I think we should be keeping 2.1.X as stable as possible, and be tidying 
trunk.

We therefore need to be thinking about how to get trunk released within 
a reasonable time (6 months?), and therefore be prepared to delay some 
features until 2.3 if their development is going to take too long.

After all, 2.1.X is a _maintenance_ branch, but that doesn't seem too 
much like how we're using it - we're adding stuff to it that should go 
in 2.2, only because we don't know when 2.2 will be out, we're not happy 
to just have it there.

Regards, Upayavira

Regards, Upayavira