Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Sender: markj@cloaked.freeserve.co.uk
To: cocoon-dev@xml.apache.org
Subject: Re: [ADMIN] process for applying patches
References: <F228rSByh133tYwlib40000b387@hotmail.com>
	<F228rSByh133tYwlib40000b387@hotmail.com>
	<20001106131121.C16145@hydrogen.internal.luminas.co.uk>
From: MJ Ray <markj@luminas.co.uk>
Organization: Luminas Ltd.  Not an official statement.
Content-Type: text/plain; charset=US-ASCII
Date: 06 Nov 2000 19:02:51 +0000
In-Reply-To: Paul Russell's message of "Mon, 6 Nov 2000 13:11:21 +0000"
Message-ID: <878zqwx6sk.fsf@cloaked.freeserve.co.uk>
Lines: 30
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef)
MIME-Version: 1.0

Paul Russell <paul@luminas.co.uk> writes:
> I think there is some place for a patch control system. If
[...]
> people can very quickly sanity check the patches and work
> out why they're doing what they're doing. Cavets with this
> are that the system would be relatively complex, and would
> need to be able to access the CVS repositories. Are there
> any CVS client libraries in java?

Actually, I suspect the biggest caveat is the time that the developers
have.  My experience on projects which use a patch control system is
that they work badly, if at all, mainly because the developers haven't
time to surf over to the patches website, but they take notice of
mailed patches.  

The ones which work best seem to have a situation similar to some
learned journals, where a patch is reviewed by one or two people who
should know the area, then forwarded to the person with responsibility
for that section of the code.  On cocoon-dev, this could be achieved
quite easily by people adhering to the [PATCH] and [C2] subject-line
conventions and savvy people constructively criticising the patch
on-list and/or to the maintainer of that section after they've tried
it out.

Of course, no two groups are developers are unique, so this advice
comes with ABSOLUTELY NO WARRANTY like all good Open Source ;-)
-- 
MJR
Luminas Ltd, Internet Applications Development
</delurk> <!-- who wants valid XML? -->