Heikki Toivonen wrote:
There are degrees of importance. For example, I think checkin comments
are very important and should contain lots of information. Some others
disagree about the importance, and think various parts I think are
important can be omitted. Discussions haven't lead to consensus. So we
are at the status quo where everyone does pretty much what they want,
because nobody considers it so important as to take really drastic
measures to force a resolution.
I disagree slightly with your characterization here.
We made a decision that we'd require bug #s in comments when the fix is
for a bug, and people seem to be following that requirement pretty
consistently.
There was also a decision (implicit, and we do need to be making
decisions more explicitly) not to enforce more detailed requirements for
checkin comments at this time. Several folks made the argument that good
checkin comments are really useful, and are following that example
themselves. As a result, more people are following suit as they see that
it is useful themselves. (Count me as one who is at least trying to do
that).
Sometimes cultural change takes a while, adding more process right away
isn't always the best way to get that to happen.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
