Re: [python-committers] Misc/NEWS entries added to released versions
Often the NEWS entry ends up being rewritten from the commit message to be more user-focussed description of the change...
On Sep 14, 2009 6:33 PM, "Georg Brandl" <g.brandl@gmx.net> wrote:
Brett Cannon schrieb:
brainstorm: >> >> It'd be nicer if we could generate the file from another source, >> perhaps ke... We should just switch to Mercurial :)
I've already hacked up a hg extension to automatically fill the commit message with the changes in a NEWS or CHANGELOG file. This works quite well -- you add the short but nice description to NEWS, do "hg commit", and the editor pops up where you can either accept the message consisting of only the changes in NEWS, or add some more stuff that's not interesting to users.
cheers, Georg
-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
_______________________________________________ python-committers mailing list python-committers@py...
Yes, but still: in many cases they are very similar.
Plus, it's hard to auto-add a NEWS entry from a commit message (because you need to determine the right section), while it's easy to pre-fill the commit message from a NEWS diff.
Georg
Anthony Baxter schrieb:
Often the NEWS entry ends up being rewritten from the commit message to be more user-focussed description of the change...
On Sep 14, 2009 6:33 PM, "Georg Brandl" <g.brandl@gmx.net <mailto:g.brandl@gmx.net>> wrote:
Brett Cannon schrieb:
brainstorm: >> >> It'd be nicer if we could generate the file from another source, >> perhaps ke...
We should just switch to Mercurial :)
I've already hacked up a hg extension to automatically fill the commit message with the changes in a NEWS or CHANGELOG file. This works quite well -- you add the short but nice description to NEWS, do "hg commit", and the editor pops up where you can either accept the message consisting of only the changes in NEWS, or add some more stuff that's not interesting to users.
On Mon, 14 Sep 2009 at 12:40, Georg Brandl wrote:
Yes, but still: in many cases they are very similar.
Plus, it's hard to auto-add a NEWS entry from a commit message (because you need to determine the right section), while it's easy to pre-fill the commit message from a NEWS diff.
But the problem we are trying to solve is the fact that the NEWS entries wind up in the _wrong_ section on merges. Any thoughts about how to solve that under Mercurial?
--David
R. David Murray schrieb:
On Mon, 14 Sep 2009 at 12:40, Georg Brandl wrote:
Yes, but still: in many cases they are very similar.
Plus, it's hard to auto-add a NEWS entry from a commit message (because you need to determine the right section), while it's easy to pre-fill the commit message from a NEWS diff.
But the problem we are trying to solve is the fact that the NEWS entries wind up in the _wrong_ section on merges. Any thoughts about how to solve that under Mercurial?
You are right, my shameless plug doesn't even solve the original problem :)
However, the fact remains that *should* someone want to write an extension that handles this the right way, it would be much much easier than for Subversion. So, before we shoot at solutions here, let's wait for the switch.
Georg
-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
On Mon, Sep 14, 2009 at 10:05 AM, R. David Murray <rdmurray@bitdance.com> wrote:
But the problem we are trying to solve is the fact that the NEWS entries wind up in the _wrong_ section on merges. Any thoughts about how to solve that under Mercurial?
Could we add a version tag to each NEWS entry? Or perhaps, we could move the content of NEWS to NEWS.history after each release? These may not be the most elegant solutions, but I think either would solve the issue.
-- Alexandre
participants (4)
-
Alexandre Vassalotti -
Anthony Baxter -
Georg Brandl -
R. David Murray