I think it should be the changelog since the last formal release. In my opinion, an updated release candidate (e.g. rc-2, rc-3 ...) should not contain new features or fix bugs. They should only fix release-related problems like license problems. Even if there is an urgent issue, we should start a new hotfix version rather than adding it in another release candidate.
Perhaps we should also discuss our version number policy in this thread. A popular method may be MAJOR.MINOR.PATCH [1]. In this case, we may add the minor version in each regular monthly release, and use patch number to version hotfix versions. Apache release policy [2] doesn't talk too much about whether release candidates could include new features or new bug fixes. Could our mentor give any advice on this? [1] https://semver.org/ [2] http://www.apache.org/legal/release-policy.html Wenli On Mon, Aug 26, 2019 at 4:04 PM SHUANG SU <sushuang0...@gmail.com> wrote: > ------------------------------ > Su Shuang (100pah) > ------------------------------ > > > > ---------- Forwarded message --------- > From: SHUANG SU <sushuang0...@gmail.com> > Date: Mon, 26 Aug 2019 at 15:56 > Subject: [DISCUSS] Changelog issue > To: <priv...@echarts.apache.org> > > > > Hi all, > > Shall we discuss a changelog issue: > > Suppose we have these versions: > 4.1.0(formal release) ==> 4.2.1-rc.1(pre-release) ==> 4.2.1(formal release) > > The changelog of 4.2.1, should be: > A. The diff with 4.1.0 > (where the major part of the changelog of 4.2.1 will be duplicated > with the changelog of 4.2.1-rc.1) > B. The diff with 4.2.1-rc.1 > (where the changelog of 4.2.1 will contain only a little content, > that is probably not appropriate for a "formal release") > > > > > > ------------------------------ > Su Shuang (100pah) > ------------------------------ >
