On Sun, 13 Sep 2009 at 13:15, Brett Cannon wrote:
On Sun, Sep 13, 2009 at 09:07, Gregory P. Smith <g...@krypto.org> wrote:
Thanks. ??One reason this happens is that our NEWS file is very
difficult to navigate. ??svnmerge rarely works on it because the
context is often different in the branch file but figuring out which
version's section of the bazillion line file you are currently in is
very tedious in a text editor.
brainstorm:
It'd be nicer if we could generate the file from another source,
perhaps keep each releases news in its own file and merge it all
together at release time?
Or have a NEWS.latest file that contains only updates since the
previous release (part of making a release would be to prepend
NEWS.latest to the NEWS file and truncate NEWS.latest)?
Or simply take the first line of each commit? I mean why do we enter
it twice? If we have a commit that is unimportant we could come up
with some convention to make it as such or simply have the comment
start with a blank line.
I think it is often good to put more information into the commit message
than should go into the NEWS entry. But having a way to mark up the
NEWS entry inside the commit message might work.
We'd need a volunteer to implement it, though :)
--David
_______________________________________________
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/python-committers
