subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <>
Subject Re: svn commit: r1817775 - /subversion/site/publish/docs/community-guide/releasing.part.html
Date Mon, 11 Dec 2017 17:15:21 GMT wrote on Mon, 11 Dec 2017 13:41 +0000:
> Modified:
>     subversion/site/publish/docs/community-guide/releasing.part.html

Could you backport this to staging/ so future changes to staging don't
merge conflict when they are published?

> +++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Dec 11 13:41:35
> @@ -1282,6 +1282,8 @@ A.B with the version you're preparing, e
>  <li><p>Ask someone with appropriate access to add the A.B.x branch to the
>         <tt>svn-role</tt> mergebot.</p></li>

I believe nowadays this managed by infra here:

It currently uses  I think it's up to you whether to have
1.10.x use (as 1.9.x does; just add 1.10.x to the for loop
there) or (the newer / shinier / non-deprecated
equivalent; tools/dist/README.backport has details).

Someone needs to run the 'svn checkout' manually.  I've just done that.
The exact checkout command is documented in machines/svn-qavm2/notes.txt
in the private repository (need to use a trunk client and the svn-master.a.o

> +<li><p>Make sure all buildbot builders are building the new release branch.</p></li>

I added 1.10.x to the buildbot config a while ago.  Now would be a good
time to add 1.11.x to it, though. :-)



View raw message