Stop updating ChangeLog?
Yao Qi <[email protected]>
| Newsgroups | gmane.comp.gdb.devel,gmane.comp.gdb.patches |
|---|---|
| Message-ID | <CAH=s-PMDK233mPHHecHbrRky3QyaWYLem8KyujWm+E6M+N1WOQ@mail.gmail.com> |
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? -- Yao (齐尧) P.S. I found that this topic has been discussed several times in various projects (binutils, glibc, etc) without any conclusions. I do hope we can make some progress this time :)