Stop updating ChangeLog?
Simon Marchi
simon.marchi@polymtl.ca
Mon Feb 5 16:30:00 GMT 2018
On 2018-02-05 11:00, Yao Qi wrote:
> Hi all,
> The discussion in this thread
> https://sourceware.org/ml/gdb-patches/2018-02/msg00012.html
> leads to a discussion that whether we still need ChangeLog. I start
> a new thread to get more attention on this topic.
>
> In current development, we need to write one ore more changelog
> entries for each commit, put them into both git commit log and
> ChangeLog files. How much we can change to existing mode
> depends the answers to these following questions,
>
> #1 Are ChangeLog files useful in GDB releases to various people
> who build GDB releases?
> #2 Are ChangeLog files useful in GDB repo to various GDB
> developers?
>
> a) If answers are Yes/Yes, we keep unchanged,
> b) If answers are No/No, we don't need to write changelog entries in
> git commit log, nor updating ChangeLog file,
> c) If answer are Yes/No, developers still have to write changelog
> entries in git commit log, and we can generate ChangeLog on
> release from git log.
> d) If answers are No/Yes, get use to git to get the information from
> git log instead of ChangeLog,
>
> My answers are No/No, so I suggest that we do b). I can live up with
> c), but that needs change in the release process. What do you think?
My answers would be No/No, though I don't build GDB releases from
tarball, so I can't really tell for #1.
I explained my point of view here:
https://sourceware.org/ml/gdb-patches/2018-02/msg00036.html
Simon
More information about the Gdb-patches
mailing list