Don't know who told you that, but we have definitely been adding WIP CHANGELOG entries on the master branch for a long time. As you mentioned this is important for reducing release manager overhead.
On Thu, Jul 6, 2017 at 9:08 PM, Jie Yu <[email protected]> wrote: > Hi folks, > > I was told that for 1.x.0 releases, we should not add WIP CHANGELOG entries > until a release candidate is cut. However, I'd argue that we should keep > adding WIP entries (mainly 'new feature' and 'deprecation') to the > CHANGELOG for 1.x.0 releases. For the ticket list, we should use the auto > generated list from JIRA when release manager cuts the release. > > I think this approach is more scalable than asking release manager to write > the new features section and the deprecation section of the CHANGELOG > during the release process. That's the same approach we took for releasing > point releases, and that turns out to work pretty well. > > Thoughts? Any objections? > > - Jie >
