Re: What about commit policy
- From: Benoit Caccinolo <bcaccinolo idealx com>
- To: Kjartan Maraas <kmaraas broadpark no>
- Cc: gnome devel-list <gnome-devel-list gnome org>, gnome list <gnome-list gnome org>, gnome devtools <gnome-devtools gnome org>
- Subject: Re: What about commit policy
- Date: Fri, 11 Feb 2005 10:18:59 +0100
On mer, 2005-02-09 at 17:23 +0100, Kjartan Maraas wrote:
>ons, 09,.02.2005 kl. 13.59 +0100, skrev Benoit Caccinolo:
>> Hi,
>>
>> I would like to know if there is some policy about cvs usage. I didn't
>> find anything about this on the website.
>>
>Mostly this is covered in individual modules' README, README.cvs,
>HACKING or similar files. We have maintainers with very different views
>on what is allowed and what is not so making a set of policies that
>match all modules is going to be hard. This is why we have had the build
>sheriff role so we could get any breakage barring people from building
>from CVS fixed as soon as possible.
Ok I see. But if we see a CVS policy as a bunch of good pieces of advice
for hackers, it could be really usefull. Take a look at the page
http://developer.kde.org/policies/commitpolicy.html , it is clear and it
can be applied to all projects. A gnome one could be great.
Cheers
--
Benoit Caccinolo bcaccinolo idealx com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]