Branko Čibej wrote on Tue, 30 Oct 2018 10:22 +0100:
> It's important enough to be added to CHANGES, in the server-side
> bugfixes section, so please add a line there, for 1.12.0.
Since we'll have to add this revision four times to CHANGES (on for each
of 1.9, 1.10, 1.11, 1.12), perhaps we should start using the CHANGES-in-log-
message convention a bit more? In this case, it would be something like
.
[U:server] mod_dav_svn, mod_authz_svn: Fix segfault under mod_http2
(SVN-4782)
.
added to the the log message (as documented in
tools/dist/release.py:write_changelog()).
(Rüdiger, this isn't something you could've known. It so happens that
today we start, for the first time in our history, to support three
minor lines in parallel; that's why I'm bringing up streamlining the
CHANGES process.)
> The backport process is similar to APR's and I assume httpd's, we use a
> STATUS file for nominations with 3 PMC +1 required for core changes. We
> have a script for proposing backports, here's an example:
We also have a script for automatically merging backports that have received
the required number of votes, which might be of interest to apr/httpd's RM's.
(See commits by the role account 'svn-role' to our tree.)
Cheers,
Daniel
