I would like to update my email address in the COMMITTERS file in the
1.6.x and 1.5.x branches.
Either a colleague of mine or a customer noticed that the COMMITTERS
file in release branches contains out-of-date email addresses. For
example, my address given in
is no longer valid, and it also implies that I work for CollabNet, which
I did when 1.5.x was branched but don't now.
Any objection to me updating my email address in the release branches to
reduce the number of such misunderstandings in future?
(Of course if everyone who looks at the file guesses that it might be
out of date and can be bothered to go and find the trunk version before
making any assumptions, there would be no problem, but we're dealing
with humans here.)
The file is not intended to indicate which company I worked for at that
time, so up-to-date email addresses are clearly better. Also, it is
clearly intended as a list of all committers to the project, not to
indicate exactly who worked on that particular release, so it does not
contain branch-specific material. In light of that, do you think it
would be better to ship the current (trunk) version of that file each
time we make a release? (This could be done in several ways - by copying
or merging at release time, or by moving it up one directory level, or
by always back-porting any updates.)
Received on 2010-01-21 20:06:48 CET