[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bugfixing for users, was: What backend should be the default now on -nix
From: |
MJ Ray |
Subject: |
bugfixing for users, was: What backend should be the default now on -nix? |
Date: |
29 Oct 2004 17:25:35 GMT |
Gregory John Casamento <greg_casamento@yahoo.com> wrote:
> Yes, they can untangle my bugfixes. For each bug I discover I document
> exactly what was fixed in the ChangeLog and I also, if a savannah bug exists,
> document the cause there AND in the ChangeLog. Also we do have a CVS mailing
> list which shows diffs when something is committed.
Few of the bugs which have hindered me, or that I investigated on the
bug tracker, have been fixed by you. That's probably my bad luck. It
sounds like you are a good developer for users to encounter.
The CVS mailing list is not much help with bugfixes today, as commit
log messages often don't reference bugs or are combined unrelated commits.
> Also, if you can point me to anywhere in the GNU Coding Standards where it
> says
> I must do one bugfix for each commit, I'll start doing that.
Nothing in the Coding Standards documents handling bugfixes at all,
as far as I can tell. I suspect this might be intended for NEWS,
but I could be wrong. I noticed that the GNUstep Coding Standards
directs developers *not* to give reasons for changes in ChangeLogs.
http://www.gnustep.org/resources/documentation/Developer/CodingStandards/coding-standards_2.html#SEC2
I suggest the Debian Developer's Reference as one example of good
practice in handling bugs.
http://www.uk.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-debian-changelog
> What level, precisely, are you talking about releasing patches at? Doing it
> at
> the individual bug level can get pretty tiresome, although this would allow
> other developers to pick and choose which changes go in, but it might become
> an
> issue since changes are sometimes interdependent.
Individual bug level, but only for potentially serious bugs found in release
versions. Would that still be too awkward?
["Fixed in CVS" closes]
> None of mine ever do, and I don't agree with this practice.
I hope your good habits are contagious.
Best wishes,
--
MJR/self
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bugfixing for users, was: What backend should be the default now on -nix?,
MJ Ray <=