Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Content-Type: text/plain;
  charset="iso-8859-1"
From: David Crossley <crossley@indexgeo.com.au>
Reply-To: crossley@indexgeo.com.au
To: cocoon-dev@xml.apache.org
Subject: Re: patch politics
Date: Sun, 16 Dec 2001 17:30:37 +1100
MIME-Version: 1.0
Message-Id: <01121615500501.09933@igacer>
Content-Transfer-Encoding: 8bit

Vadim Gritsenko wrote:
> Giacomo Pati wrote:
>> Vadim Gritsenko wrote:
>>> Giacomo Pati wrote:
>>>> Well, I'll clean up the HEAD branch slowly but I don't have
>>>> the time to do it in the 2.0 branch as well. I'd suggest to move
>>>> the head to release quality and only patch the 2.0 branch
>>>> for bugs. This way we can get rid of the 2.0 branch sooner
>>>> than later (which was always the proposed way to go IIRC).
>>>
>>> There is one problem with going with HEAD only: HEAD contains some
>>> experimental/unverified/new code, and people always will come with
>>> something new (so this situation won't change with time), and in
>>> contrast with that, branch gets only stable/voted code.
>>
>> Sorry, but there is a scratchpad area where such code can live. It has
>> to be moved there if that code is not stable enough.
>
> Cool. Then we need to cleanup HEAD a little bit and rollout 2.0.1
> release out of it.
> Vadim

Whoa, hold on. I thought that the whole of HEAD was an
experimentation area. I remember the Cocoon documentation
saying that, though i cannot find it now.

There is more required that just a scratchpad dir for new
Java code ... new samples, new and updated xdocs, config
experimentation (e.g. validation during build docs).

Perhaps the purpose of each branch should be clearly
defined and documented in contrib.xml
--David

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org