[Twisted-Python] Re: [Twisted-commits] CVS: Twisted ChangeLog,1.13,1.14
For those of you who do not subscribe, this is a message in response to a CVS commit. If you're interested in getting CVS commit messages, email me privately. On Mon, 2002-02-11 at 16:02, Chris Armstrong wrote:
Update of /cvs/Twisted In directory zaibach:/tmp/cvs-serv21198
Modified Files: ChangeLog Log Message: updated ChangeLog to reflect stuff on twisted-commits.
IMHO this is far too fine-grained. Especially something like:
+ * twisted/eco/eco.py: Reverted evaluator state back to functional-ness + :) And added functions (anonymous and global), and broke various + interfaces
Not to mention the fact that the evaluator is hardly functional, even though it uses functions :) In general, NOTHING that gets changed in CVS and then gets changed *back* before the release ought to be documented in ChangeLog. This is confusing enough as is. -- "Cannot stand to be one of many -- I'm not what they are." -Guster, "Rocketship" glyph lefkowitz; ninjaneer, freelance demiurge glyph @ [ninjaneering|twistedmatrix].com
Well, the main reason for that entry was Functions, because that was a pretty large milestone (at least I was proud of it. :)). I just put in the other stuff because I happened to do it at the same time. On Mon, 2002-02-11 at 19:51, Glyph Lefkowitz wrote:
For those of you who do not subscribe, this is a message in response to a CVS commit. If you're interested in getting CVS commit messages, email me privately.
On Mon, 2002-02-11 at 16:02, Chris Armstrong wrote:
Update of /cvs/Twisted In directory zaibach:/tmp/cvs-serv21198
Modified Files: ChangeLog Log Message: updated ChangeLog to reflect stuff on twisted-commits.
IMHO this is far too fine-grained. Especially something like:
+ * twisted/eco/eco.py: Reverted evaluator state back to functional-ness + :) And added functions (anonymous and global), and broke various + interfaces
Not to mention the fact that the evaluator is hardly functional, even though it uses functions :)
In general, NOTHING that gets changed in CVS and then gets changed *back* before the release ought to be documented in ChangeLog. This is confusing enough as is.
-- "Cannot stand to be one of many -- I'm not what they are." -Guster, "Rocketship" glyph lefkowitz; ninjaneer, freelance demiurge glyph @ [ninjaneering|twistedmatrix].com -- Chris Armstrong << radix@twistedmatrix.com >> http://twistedmatrix.com/users/carmstro.twistd/
On Mon, 2002-02-11 at 16:51, Glyph Lefkowitz wrote:
IMHO this is far too fine-grained. Especially something like:
I'll say it again. If you don't want your ChangeLog file to have the stuff the rest of the world puts in their ChangeLog files, then maybe you're thinking of a different file. [Where "rest of the world" is most everything in the GIMP-based universe, the parts of the Linux kernel which actually have a ChangeLog, glibc, quadra, etc.] When I write in a ChangeLog, I'm writing for other developers, and probably developers who are working on the code NOW, not necessarily after its release. If you want a feature-level overview to refer to from the release announcement, call it NEWS. If you want a few more technical details, call it "release notes" (relnotes). Yes, this does overlap with CVS commit messages. But if you're working with a checked out copy of the code and you're off-line, you may not have access to the CVS logs or commits-list archives. log-edit-insert-changelog gets run by cvs-commit-setup for a reason, and don't be afraid to use cvs-add-change-log-entry as emacs intended. -- The moon is new, 0.2% illuminated, 29.1 days old.
participants (3)
-
Christopher Armstrong -
Glyph Lefkowitz -
Kevin Turner