Re: 1.10 tasks: update CHANGES and roll RC1 or beta1
From: Stefan Sperling <stsp_at_apache.org>
Date: Mon, 25 Dec 2017 14:20:07 +0100
On Mon, Dec 25, 2017 at 12:21:46PM +0100, Stefan Fuhrmann wrote:
Thanks! This helps a lot with completing the changelog.
However, I have some mild concerns.
I don't think it makes sense to list changes such as:
> * Add support for tracing moves backwards in history to the conflict
> * Make svn --non-interactive use recommended tree conflict resolution
> * fsfs: Don't store SHA1 for property representations in format 8.
Because these are not changes relative to 1.9, they are changes made
Also, entries such as:
> * Fix a slightly broken private API. (r1807966)
> * Refactor the merging of merge rangelists (r1802470 et al)
> * Merge the 'shelve' branch to trunk. (r1815228 et al)
> * release.py: Don't discard errors. (r1804278)
provide little value to end users. They don't convey enough information
The changelog should not be a mirror of what the commit log says.
I spent about a day and a half already on many 1.10 changelog entries,
On the bright side, there are some entries the script found which are
> * Add a new --vacuum-pristines option to 'svn cleanup'. (r1802787
> * Add '--include' and '--exclude' options to 'svnadmin dump'.
> * svnadmin: Introduce the `--normalize-props` option for the load
I am not going to go through all of these now. I suppose you already
This is an archived mail posted to the Subversion Dev mailing list.