cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <nicola...@supereva.it>
Subject Re: [ADMIN] process for applying patches
Date Tue, 07 Nov 2000 16:18:44 GMT
From: "MJ Ray" <markj@luminas.co.uk>
> 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.

+1.
Also devs can filter their male by words in subject ([C2], [PATCH]) so to
obtain
benefits as of both methods mentioned prior in the mails.

nicola_ken


Mime
View raw message