On Tue, Oct 11, 2005 at 12:14:20AM +0200, Nils Kneuper wrote:
> I still think that it would be the easiest solution to simply have
> every dev simply make sure that his commit directly goes into the
> changelog.
Problem is, IIRC we already tried this approach :)
> I think the automated systems could be problematic, too. If every
> dev makes sure that the stuff changed is in there it would be fine.
Sure, but well, the only way I can think of reminding all devs to
update the changelog is to force (via a pre-commit hook) evey commit
to touch the changelog. It is obviously far too strong, and could at
1st thought only get justified of we add something of a "svn internal"
section in the changelog, to be deleted during pre-release cleanup.
But it would basically duplicate the svn log messages, so we would
risk to drift towards lower-quality log messages, which is even worse.
And it would basically only be a manual version of a list that we
could automatically generate for the most part :)
OTOH, having classified bugs in gna!, and referencing all of them in
log messages, we could get most of the changelog production automated.
And since the classification work does not have to be done twice,
taking care of the bugtracker would surely be less of an ingrateful job.
Sure, it would involve having open tickets in gna! for every new
feature or issue, and we may have to force every log message to
include a "bug NNN" reference, and the final changelog will surely
require manual editting in the end. But nonetheless, I think it could
globally benefit to the project.
Best regards,
--
Yann Dirson <[EMAIL PROTECTED]> |
Debian-related: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
