Hello,
The 5.15.0 release candidate 1 seems to work OK to judge by
the lack of complaints. A few minor changes have been
committed to the release branch. What I would like to do at this
point is to tag the existing stuff on the release branch
(rc1 + accumulated changes) and release it as 5.15.0.
If some more changes are required (in particular if there are
installation problems) then we can commit a fix to
the release branch and release 5.15.1.
I'd like to change the release process to do away with the
release candidates and just release x.y.0 as the first version
on a release branch, then x.y.1, x.y.2 etc as necessary.
The main difference wrt the current scheme is that the
current scheme requires a redundant re-release of the
final release candidate as the official x.y.0.
There's no need for that.
Also I think the x.y.0, x.y.1, etc scheme is slightly more rational.
Your friendly project administrator,
Robert Dodier