On Thu, May 17, 2007 at 12:12:14AM +0300, Dov Feldstern wrote: > If I get access, could you please just send me a short refresher on the > procedure --- do we still have to update anything besides the commit > log?
No, we do not maintain ChangeLog files anymore. Just write a descriptive log messages, preferably mention potential areas of conflict. > Does a patch sent to the mailing list with "any objections?", and > which does not receive objections, qualify for commit? There are no strict rules, but maybe we should set up a few guidelines when more people get write access. My personal recommendation for 'newcomers' (i.e. people that have been around for a while and already got some of their stuff committed by others) are something like the following: Depending on the severity: Purely cosmetical, small scale changes (correcting spelling mistakes in comments, whitespace changes or so) should be sent to the list. Can be committed after a grace period of a few hours. If it is 'really obvious', wait a day or two or (preferably) you get an explicit 'ok', then commit. If it is 'easy' and in 'your playground' (which would be RTL in this case) better wait for explicit consent or resent after a couple of days and then commit. If it is 'business as usual in your playground' try to get affirmation, even twice. Changes to area of the code outside your playground should be discussed. For thing like changing default settings try to reach consensus. Then 'business as usual'. Severe changes to the core should only happen after reaching consensus on the list, i.e. usuall four or five people in favour and the rest not being vocal about their dissent. After a while, you may bump all rules by a level, and after a few decades you'll invent rules by yourself... Andre'
