Author: hartmannathan Date: Fri Nov 1 04:00:32 2019 New Revision: 1869231 URL: http://svn.apache.org/viewvc?rev=1869231&view=rev Log: [On the staging-ng branch] * Bring up to date with staging
Added: subversion/site/staging-ng/docs/release-notes/1.13.html - copied unchanged from r1869230, subversion/site/staging/docs/release-notes/1.13.html Modified: subversion/site/staging-ng/ (props changed) subversion/site/staging-ng/.message-ids.tsv subversion/site/staging-ng/doap.rdf subversion/site/staging-ng/docs/community-guide/releasing.part.html subversion/site/staging-ng/docs/release-notes/index.html subversion/site/staging-ng/docs/release-notes/release-history.html subversion/site/staging-ng/download.html subversion/site/staging-ng/index.html (contents, props changed) subversion/site/staging-ng/news.html (contents, props changed) subversion/site/staging-ng/roadmap.html (contents, props changed) subversion/site/staging-ng/style/site.css subversion/site/staging-ng/upcoming.part.html Propchange: subversion/site/staging-ng/ ------------------------------------------------------------------------------ Merged /subversion/site/publish:r1867062-1869118 Merged /subversion/site/staging:r1867728-1869230 Modified: subversion/site/staging-ng/.message-ids.tsv URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/.message-ids.tsv?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/.message-ids.tsv (original) +++ subversion/site/staging-ng/.message-ids.tsv Fri Nov 1 04:00:32 2019 @@ -1,5 +1,5 @@ # Message-ids of archived emails that are referenced by a svn.haxx.se URL. -# Generated by tools/haxx-url-to-message-id.sh on 2019-08-03 +# Generated by tools/haxx-url-to-message-id.sh on 2019-09-19 https://svn.haxx.se/dev/archive-2003-01/1125.shtml 20030116213052.314004c1.tt...@idsoftware.com https://svn.haxx.se/dev/archive-2003-02/0068.shtml 87wuki4fpy....@codematters.co.uk https://svn.haxx.se/dev/archive-2003-10/0136.shtml 200310031235.h93czgiv064...@bigtex.jrv.org @@ -43,6 +43,7 @@ https://svn.haxx.se/dev/archive-2015-08/ https://svn.haxx.se/dev/archive-2017-07/0054.shtml 20170707111125.gc53...@jessup.stsp.name https://svn.haxx.se/dev/archive-2019-03/0012.shtml fbbd2c2c-0287-4486-9177-e532ba45f...@ikoder.com https://svn.haxx.se/dev/archive-2019-04/0020.shtml 0ca0045a-7f19-b22b-b184-535275371...@apache.org +https://svn.haxx.se/dev/archive-2019-07/0072.shtml CALq3gdNT2z3eh8DffprebV+XzifAR8CqbgGgs7id1NA4Ui=z...@mail.gmail.com https://svn.haxx.se/users/archive-2004-03/0488.shtml 1078601435.31293.104.ca...@madison.badger.com https://svn.haxx.se/users/archive-2004-07/1662.shtml 003c01c4763b$180511f0$800000c0@blazepoint.local https://svn.haxx.se/users/archive-2010-01/0001.shtml 69b68910-b4d0-428e-a4bb-fb7d6e87b...@barrys-emacs.org Modified: subversion/site/staging-ng/doap.rdf URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/doap.rdf?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/doap.rdf (original) +++ subversion/site/staging-ng/doap.rdf Fri Nov 1 04:00:32 2019 @@ -36,9 +36,9 @@ <category rdf:resource="http://projects.apache.org/category/build-management" /> <release> <Version> - <name>Current 1.12 regular release</name> - <created>2019-07-24</created> - <revision>1.12.2</revision> + <name>Current 1.13 regular release</name> + <created>2019-10-30</created> + <revision>1.13.0</revision> </Version> </release> <release> Modified: subversion/site/staging-ng/docs/community-guide/releasing.part.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/docs/community-guide/releasing.part.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/docs/community-guide/releasing.part.html (original) +++ subversion/site/staging-ng/docs/community-guide/releasing.part.html Fri Nov 1 04:00:32 2019 @@ -89,7 +89,7 @@ In order from least- to most-stable:</p> <td>Beta</td> <td>We don't expect there to be problems, but be wary just in case.</td> <td><tt>subversion-1.7.0-beta1</tt></td> - <td>version 1.7.0 (Beta 2)</td> + <td>version 1.7.0 (Beta 1)</td> </tr> <tr> <td>RC (Release Candidate)</td> @@ -685,21 +685,20 @@ it.</p> title="Link to this section">¶</a> </h4> -<p><b>For a non-LTS ("regular") release line</b></p> - -<p>A change is approved if it receives two +1s and no vetoes. (Only +<p>For a <b>non-LTS ("regular") release line</b>, +a change is approved if it receives <b>two +1s</b> and no vetoes. (Only binding votes count; see above.)</p> -<p><b>For an LTS release line</b></p> - -<p>A change is approved if it receives three +1s and no vetoes. (Only +<p>For an <b>LTS release line</b>, +a change is approved if it receives <b>three +1s</b> and no vetoes. (Only binding votes count; see above.)</p> -<p>Notwithstanding the above, a change that affects only areas that are not -core code (for example, tools/, packages/, bindings/, test scripts, etc.), -and that does <em>not</em> affect the build system, -can go in with a +1 from a full committer or a -partial committer for that area, at least one +0 or "concept +1" from +<p>Notwithstanding the above, for any release line, a change that +affects only areas that are <b>not core code</b> (for example, +tools/, packages/, bindings/, test scripts, etc.), +and that does <b>not affect the build system</b>, +can go in with <b>one +1</b> from a full committer or a +partial committer for that area, at least <b>one +0</b> or "concept +1" from any other committer, and no vetoes.</p> <p>The goal is to get at least two @@ -843,7 +842,7 @@ special build tools for Subversion RM du software with the <tt>release.py build-env</tt> command. <pre> -mkdir -p /opt/svnrm && cd /opt/svnrm && $HOME/wc/svn/tools/dist/release.py build-env X.Y.Z +mkdir -p /opt/svnrm && cd /opt/svnrm && $SVN_SRC_DIR/tools/dist/release.py build-env X.Y.Z </pre> </div> <!-- before-release --> @@ -977,7 +976,7 @@ When release.py is done you'll have tarb <p><b>Use GnuPG to sign release:</b></p> Use release.py to sign the release: <pre> - release.py sign-candidates --target /opt/svnrm/deploy X.Y.Z + release.py sign-candidates X.Y.Z </pre> This will run the equivalent of the following commands for you: <pre> @@ -1121,7 +1120,7 @@ Verify the release manager's PGP signatu automates this step: <pre> release.py get-keys - release.py check-sigs 1.7.8 --target /path/to/dist/working/copy + release.py --target <i>/path/to/dist/dev/subversion/wc</i> check-sigs <i>1.7.0-rc4</i> </pre> </p> @@ -1134,7 +1133,7 @@ To append your signature to a .asc file, </pre> The release.py script can automate this step: <pre> - release.py sign-candidates --target /path/to/dist/dev/subversion/working/copy 1.7.0 + release.py --target <i>/path/to/dist/dev/subversion/wc</i> sign-candidates <i>1.7.0-rc4</i> </pre> <p>After adding your signatures, commit the locally modified .asc files @@ -1146,8 +1145,8 @@ to download and test it separately. The <tt>.bz2</tt> file, and pack it using <tt>gzip</tt> like this:</p> <pre> - bzip2 -cd subversion-1.3.0-rc4.tar.bz2 \ - | gzip -9n > subversion-1.3.0-rc4.tar.gz + bzip2 -cd subversion-1.7.0-rc4.tar.bz2 \ + | gzip -9n > subversion-1.7.0-rc4.tar.gz </pre> <p>The resulting file should be identical to the file generated by the @@ -1438,7 +1437,15 @@ A.B with the version you're preparing, e <h4>Automated</h4> <p>Run this in an empty-ish directory where it will make some temporary checkouts:</p> -<pre>$SVN_SRC_DIR/tools/dist/create-minor-release-branch.py create-release-branch --verbose A.B.0</pre> +<pre> +release.py --verbose create-release-branch A.B.0 +</pre> +<p>Write a release notes template:</p> +<pre> +release.py --verbose write-release-notes A.B.0 > .../docs/release-notes/A.B.html +svn add .../docs/release-notes/A.B.html +svn ci -m "Add release notes template." .../docs/release-notes/A.B.html +</pre> <div class="notice">Some steps are not automated—highlighted below.</div> <h4>Manual Steps</h4> @@ -1495,26 +1502,64 @@ A.B with the version you're preparing, e <li><p>Create a new <tt>STATUS</tt> file on the release branch.</p></li> -<li><div class="notice">This step is not automated.</div> - <p>Ask someone with appropriate access to add the A.B.x branch to the - <tt>svn-role</tt> backport mergebot:</p> - <p>Submit a pull-request on GitHub to add 'A.B.x' to the list in <a - href="https://github.com/apache/infrastructure-puppet/edit/deployment/modules/svnqavm_pvm_asf/manifests/init.pp">https://github.com/apache/infrastructure-puppet/edit/deployment/modules/svnqavm_pvm_asf/manifests/init.pp</a></p> - - <p>Someone needs to run the 'svn checkout' manually. - 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 - hostname).</p> - </li> - <li><p>Make sure all buildbot builders are building the new release branch.</p> <p>Add A.B to the MINOR_LINES list in <a href="https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/subversion.conf">https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/subversion.conf</a>.</p></li> +<li><p>Create a template release-notes document, + <tt>site/publish/docs/release-notes/A.B.html</tt></p></li> +</ul> + +<div class="notice">The following steps are not automated:</div> +<ul> +<li> + <p>Ask someone with appropriate access to add the A.B.x branch to the + <a href="#backport-merge-bot">backport merge bot</a>.</p> + </li> </ul> </div> <!-- creating-branch --> +<div class="h3" id="backport-merge-bot"> +<h3>Managing the Backport Merge Bot + <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#backport-merge-bot" + title="Link to this section">¶</a> +</h3> +<p>The backport merge bot runs nightly on the <tt>svn-qavm</tt> machine, + under the <tt>svnsvn</tt> local user account, making commits + using the <tt>svn-role</tt> Subversion account name. </p> +<p>This configuration currently requires someone with admin access to + the machine, to manage changes to the set of branches.</p> +<p>The bot merges approved backports on each branch A.B.x for which a + WC directory exists at <tt>~svnsvn/src/svn/A.B.x</tt> .</p> +<p>The checkout there was created by running (as <tt>svnsvn</tt> user, + e.g. with sudo) something like:</p> +<pre> +svn checkout --depth=empty https://svn-master.apache.org/repos/asf/subversion/branches ~svnsvn/src/svn +svn up ~svnsvn/src/svn/<i>A.B.x</i> # for each supported branch +</pre> +<p>The repo URL is <tt>svn-master.a.o</tt> because the backports merger runs + <tt>svn ci && svn up</tt> in a loop, and assumes <tt>svn up</tt> will + update it to the revision it just committed. That's <a href="/issue4761" + >not guaranteed</a> + when updating from a mirror (and <tt>svn.a.o</tt> may point to a + mirror). The buildbot slaves do this too, for the same reason.</p> +<p>Each branch is in a subdirectory of the WC root. To add a new + branch, populate the source tree with <tt>svn up</tt>:</p> +<pre> +sudo -H -u svnsvn svn up ~svnsvn/src/svn/A.B.x +</pre> +<p>To remove a no-longer-supported branch, use <tt>svn up -r0</tt>:</p> +<pre> +sudo -H -u svnsvn svn up -r0 ~svnsvn/src/svn/Z.Z.x +</pre> +<p><i>[Historical notes can be found in <tt>machines/svn-qavm/</tt> and + <tt>machines/svn-qavm2/</tt> in the Subversion PMC's + <a href="https://svn.apache.org/repos/private/pmc/subversion"> + private repository</a>.]</i></p> + +</div> <!-- backport-merge-bot --> + <div class="h3" id="porting-changes"> <h3>Porting changes to a release branch <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#porting-changes" @@ -1549,7 +1594,7 @@ release, it must be brought up to date t last release.</p> <p>Below, we describe the manual process. For partial automation, see -<pre>tools/dist/release.py write-changelog</pre> +<pre>release.py write-changelog</pre> </p> <p>For patch-releases, this is fairly easy: you just need to walk Modified: subversion/site/staging-ng/docs/release-notes/index.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/docs/release-notes/index.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/docs/release-notes/index.html (original) +++ subversion/site/staging-ng/docs/release-notes/index.html Fri Nov 1 04:00:32 2019 @@ -47,7 +47,7 @@ official support status for the various <p>Here are the release notes for the major Subversion releases:</p> <ul> -<li><a href="1.13.html">Subversion 1.13</a> â <i>in progress</i></li> +<li><a href="1.13.html">Subversion 1.13</a> â (<i>first released â November 30, 2019</i>)</li> <li><a href="1.12.html">Subversion 1.12</a> â (<i>first released â April 24, 2019</i>)</li> <li><a href="1.11.html">Subversion 1.11</a> â Improved shelving, checkpointing, improved tree conflict resolution (<i>first released â October 30, 2018</i>)</li> <li><a href="1.10.html">Subversion 1.10</a> â Improved path-based authz, new interactive conflict resolver, LZ4 compression, FSFS format 8, shelving (<i>first released â April 12, 2018</i>)</li> @@ -108,7 +108,7 @@ official support status for the various </thead> <tbody> <tr> -<td>1.12.x</td> +<td>1.13.x</td> <td>Regular Release</td> </tr> <tr> Modified: subversion/site/staging-ng/docs/release-notes/release-history.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/docs/release-notes/release-history.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/docs/release-notes/release-history.html (original) +++ subversion/site/staging-ng/docs/release-notes/release-history.html Fri Nov 1 04:00:32 2019 @@ -31,6 +31,9 @@ Subversion 2.0.</p> <ul> <li> + <b>Subversion 1.13.0</b> (Wednesday, 30 November 2019): Feature and bugfix release, see the <a href="/docs/release-notes/1.13.html">release notes</a>. + </li> + <li> <b>Subversion 1.12.2</b> (Wednesday, 24 July 2019): Bugfix release. </li> <li> Modified: subversion/site/staging-ng/download.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/download.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/download.html (original) +++ subversion/site/staging-ng/download.html Fri Nov 1 04:00:32 2019 @@ -17,7 +17,7 @@ <h1>Download Source Code</h1> -[define version]1.12.2[end] +[define version]1.13.0[end] <div class="notice"> <p>Learn about our new 6-month regular and 2-year LTS release schedule: see @@ -105,31 +105,29 @@ Other mirrors: <p><a href="/roadmap.html#release-planning">Regular releases</a> are supported for <b>6 months</b>.</p> -<p style="font-size: 150%; text-align: center;">Apache Subversion 1.12.2</p> +<p style="font-size: 150%; text-align: center;">Apache Subversion 1.13.0</p> <table class="centered"> <tr> <th>File</th> <th>Checksum (SHA512)</th> <th>Signatures</th> + <th>PGP Public Keys</th> </tr> <tr> - <td><a href="[preferred]subversion/subversion-1.12.2.tar.bz2">subversion-1.12.2.tar.bz2</a></td> - <!-- The sha512 line does not have a class="checksum" since the link needn't - be rendered in monospace. --> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.tar.bz2.sha512">SHA-512</a>]</td> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.tar.bz2.asc">PGP</a>]</td> -</tr><tr> - <td><a href="[preferred]subversion/subversion-1.12.2.tar.gz">subversion-1.12.2.tar.gz</a></td> - <!-- The sha512 line does not have a class="checksum" since the link needn't - be rendered in monospace. --> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.tar.gz.sha512">SHA-512</a>]</td> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.tar.gz.asc">PGP</a>]</td> -</tr><tr> - <td><a href="[preferred]subversion/subversion-1.12.2.zip">subversion-1.12.2.zip</a></td> - <!-- The sha512 line does not have a class="checksum" since the link needn't - be rendered in monospace. --> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.zip.sha512">SHA-512</a>]</td> - <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.12.2.zip.asc">PGP</a>]</td> + <td><a href="[preferred]subversion/subversion-1.13.0.tar.bz2">subversion-1.13.0.tar.bz2</a></td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.tar.bz2.sha512">SHA-512</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.tar.bz2.asc">PGP signatures</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.KEYS">PGP keyring</a>]</td> +</tr><tr> + <td><a href="[preferred]subversion/subversion-1.13.0.tar.gz">subversion-1.13.0.tar.gz</a></td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.tar.gz.sha512">SHA-512</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.tar.gz.asc">PGP signatures</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.KEYS">PGP keyring</a>]</td> +</tr><tr> + <td><a href="[preferred]subversion/subversion-1.13.0.zip">subversion-1.13.0.zip</a></td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.zip.sha512">SHA-512</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.zip.asc">PGP signatures</a>]</td> + <td>[<a href="https://www.apache.org/dist/subversion/subversion-1.13.0.KEYS">PGP keyring</a>]</td> </tr> </table> @@ -262,7 +260,7 @@ Other mirrors: Subversion as to HTTP Server.)</p> <p>The PGP signatures can be verified using PGP or GPG. First download - the <a href="https://people.apache.org/keys/group/subversion.asc" + the <a href="https://www.apache.org/dist/subversion/KEYS" >KEYS</a> as well as the <code>asc</code> signature file for the particular distribution. Make sure you get these files from the <a href="https://www.apache.org/dist/subversion/" >main distribution Modified: subversion/site/staging-ng/index.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/index.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/index.html (original) +++ subversion/site/staging-ng/index.html Fri Nov 1 04:00:32 2019 @@ -66,6 +66,48 @@ <!-- In general, we'll keep only the most recent 3 or 4 news items here. --> +<div class="h3" id="news-20191030"> +<h3>2019-10-30 — Apache Subversion 1.13.0 Released + <a class="sectionlink" href="#news-20191030" + title="Link to this section">¶</a> +</h3> + +<p>We are pleased to announce the release of Apache Subversion 1.13.0. + This is the most complete Subversion release to date, and we encourage + users of Subversion to upgrade as soon as reasonable. + Please see the + <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org" + >release announcement</a> and the + <a href="/docs/release-notes/1.13" + >release notes</a> for more information about this release.</p> + +<p>To get this release from the nearest mirror, please visit our + <a href="/download.cgi#recommended-release">download page</a>.</p> + +</div> <!-- #news-20191030 --> + +<div class="h3" id="news-20190930"> +<h3>2019-09-30 — Apache Subversion 1.13.0-rc1 Released + <a class="sectionlink" href="#news-20190930" + title="Link to this section">¶</a> +</h3> + +<p>We are pleased to announce the release of Apache Subversion 1.13.0-rc1. This + release is not intended for production use, but is provided as a milestone + to encourage wider testing and feedback from intrepid users and maintainers. + Please see the + <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org">release + announcement</a> for more information about this release, and the + <a href="/docs/release-notes/1.13.html">release notes</a> and + <a href="https://svn.apache.org/repos/asf/subversion/tags/1.13.0-rc1/CHANGES"> + change log</a> for information about what will eventually be + in the 1.13.0 release.</p> + +<p>To get this release from the nearest mirror, please visit our + <a href="/download.cgi#pre-releases">download page</a>.</p> + +</div> <!-- #news-20190930 --> + <div class="h3" id="news-20190731"> <h3>2019-07-31 — Apache Subversion Security Advisory <a class="sectionlink" href="#news-20190731" @@ -88,48 +130,6 @@ </div> <!-- #news-20190731 --> -<div class="h3" id="news-20190724"> -<h3>2019-07-24 — Apache Subversion 1.12.2, 1.10.6, 1.9.12 Released - <a class="sectionlink" href="#news-20190724" - title="Link to this section">¶</a> -</h3> - -<p>We are pleased to announce the release of Apache Subversion 1.12.2, 1.10.6, 1.9.12. - This is the most complete release of each release line to date, - and we encourage all users to upgrade as soon as reasonable. - Please see the - <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org" - >release announcement</a> and the release notes ( - <a href="/docs/release-notes/1.12">1.12</a>, - <a href="/docs/release-notes/1.10">1.10</a>, - <a href="/docs/release-notes/1.9">1.9</a>) - for more information about these releases.</p> - -<p>To get this release from the nearest mirror, please visit our - <a href="/download.cgi">download page</a>.</p> - -</div> <!-- #news-20190724 --> - -<div class="h3" id="news-20190424"> -<h3>2019-04-24 — Apache Subversion 1.12.0 Released - <a class="sectionlink" href="#news-20190424" - title="Link to this section">¶</a> -</h3> - -<p>We are pleased to announce the release of Apache Subversion 1.12.0. - This is the most complete release of the 1.12.x line to date, - and we encourage all users to upgrade as soon as reasonable. - Please see the - <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org" - >release announcement</a> and the - <a href="/docs/release-notes/1.12" - >release notes</a> for more information about this release.</p> - -<p>To get this release from the nearest mirror, please visit our - <a href="/download.cgi">download page</a>.</p> - -</div> <!-- #news-20190424 --> - <p style="font-style: italic; text-align: right;">[Click <a href="/news.html">here</a> to see all News items.]</p> Propchange: subversion/site/staging-ng/index.html ------------------------------------------------------------------------------ Merged /subversion/site/staging/index.html:r1867728-1869230 Merged /subversion/site/publish/index.html:r1867062-1869118 Modified: subversion/site/staging-ng/news.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/news.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/news.html (original) +++ subversion/site/staging-ng/news.html Fri Nov 1 04:00:32 2019 @@ -22,6 +22,48 @@ <!-- Maybe we could insert H2's to split up the news items by --> <!-- calendar year if we felt the need to do so. --> +<div class="h3" id="news-20191030"> +<h3>2019-10-30 — Apache Subversion 1.13.0 Released + <a class="sectionlink" href="#news-20191030" + title="Link to this section">¶</a> +</h3> + +<p>We are pleased to announce the release of Apache Subversion 1.13.0. + This is the most complete Subversion release to date, and we encourage + users of Subversion to upgrade as soon as reasonable. + Please see the + <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org" + >release announcement</a> and the + <a href="/docs/release-notes/1.13" + >release notes</a> for more information about this release.</p> + +<p>To get this release from the nearest mirror, please visit our + <a href="/download.cgi#recommended-release">download page</a>.</p> + +</div> <!-- #news-20191030 --> + +<div class="h3" id="news-20190930"> +<h3>2019-09-30 — Apache Subversion 1.13.0-rc1 Released + <a class="sectionlink" href="#news-20190930" + title="Link to this section">¶</a> +</h3> + +<p>We are pleased to announce the release of Apache Subversion 1.13.0-rc1. This + release is not intended for production use, but is provided as a milestone + to encourage wider testing and feedback from intrepid users and maintainers. + Please see the + <a href="https://lists.apache.org/list.html?annou...@subversion.apache.org">release + announcement</a> for more information about this release, and the + <a href="/docs/release-notes/1.13.html">release notes</a> and + <a href="https://svn.apache.org/repos/asf/subversion/tags/1.13.0-rc1/CHANGES"> + change log</a> for information about what will eventually be + in the 1.13.0 release.</p> + +<p>To get this release from the nearest mirror, please visit our + <a href="/download.cgi#pre-releases">download page</a>.</p> + +</div> <!-- #news-20190930 --> + <div class="h3" id="news-20190731"> <h3>2019-07-31 — Apache Subversion Security Advisory <a class="sectionlink" href="#news-20190731" Propchange: subversion/site/staging-ng/news.html ------------------------------------------------------------------------------ Merged /subversion/site/publish/news.html:r1867062-1869118 Merged /subversion/site/staging/news.html:r1867728-1869230 Modified: subversion/site/staging-ng/roadmap.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/roadmap.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/roadmap.html (original) +++ subversion/site/staging-ng/roadmap.html Fri Nov 1 04:00:32 2019 @@ -51,11 +51,6 @@ </thead> <tbody> <tr> - <td>2019-04</td> - <td>Release 1.12.0</td> - <td></td> - </tr> - <tr> <td>2019-10</td> <td>Release 1.13.0</td> <td></td> @@ -260,18 +255,18 @@ better plan their upgrade cycles, partic <div class="h2" id="next-release-status"> -<h2>Next Release Status (Subversion 1.12) +<h2>Next Release Status <a class="sectionlink" href="#next-release-status" title="Link to this section">¶</a> </h2> -<div class="notice"> -<p> - For up-to-date information about the 1.12 release, please see the <a - href="/docs/release-notes/1.12.html">release notes</a>. -</p> -</div> +<p>Draft release notes are added to the + <a href="docs/release-notes/">release notes index</a> + some time before each release is published.</p> + +<p class="todo">OUT OF DATE</p> +<del> <p>The following table contains items currently targetted for the subsequent major release, along with their completion status. It is meant mainly for developers, but can help answer the oft-asked question "how is the next @@ -323,6 +318,7 @@ better plan their upgrade cycles, partic </tbody> </table> +</del> </div> <!-- #next-release-status --> Propchange: subversion/site/staging-ng/roadmap.html ------------------------------------------------------------------------------ Merged /subversion/site/publish/roadmap.html:r1867062-1869118 Merged /subversion/site/staging/roadmap.html:r1867728-1869230 Modified: subversion/site/staging-ng/style/site.css URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/style/site.css?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/style/site.css (original) +++ subversion/site/staging-ng/style/site.css Fri Nov 1 04:00:32 2019 @@ -275,9 +275,6 @@ table.task-table .deferred .task-name { font-size: 50%; vertical-align: super; } -.checksum { - font-family: monospace; -} /* * Hide class="sectionlink", except when an enclosing heading Modified: subversion/site/staging-ng/upcoming.part.html URL: http://svn.apache.org/viewvc/subversion/site/staging-ng/upcoming.part.html?rev=1869231&r1=1869230&r2=1869231&view=diff ============================================================================== --- subversion/site/staging-ng/upcoming.part.html (original) +++ subversion/site/staging-ng/upcoming.part.html Fri Nov 1 04:00:32 2019 @@ -146,6 +146,34 @@ Merge <a href="https://svn.apache.org/r1 +1: stsp, rhuijben, brane ------------------------------------------------------------------------ +<a href="https://svn.apache.org/r1867093">r1867093</a> | svn-role | 2019-09-18 04:00:06 +0000 (Wed, 18 Sep 2019) | 10 lines + +Merge <a href="https://svn.apache.org/r1864440">r1864440</a> from trunk: + + * <a href="https://svn.apache.org/r1864440">r1864440</a> + Fix 'svn patch' setting UNIX permissions to 0600 on files with props. + Justification: + 'svn patch' should honour the user's umask. + User complained: https://svn.haxx.se/dev/archive-2019-07/0072.shtml + Votes: + +1: stsp, brane + +------------------------------------------------------------------------ +<a href="https://svn.apache.org/r1867094">r1867094</a> | svn-role | 2019-09-18 04:00:09 +0000 (Wed, 18 Sep 2019) | 12 lines + +Merge <a href="https://svn.apache.org/r1866425">r1866425</a> from trunk: + + * <a href="https://svn.apache.org/r1866425">r1866425</a> + mod_dav_svn: Set Last-Modified response header for 'external' GET requests. + Justification: + The Last-Modified header was removed in <a href="https://svn.apache.org/r1724790">r1724790</a> for performance reasons. + However, for external requests the Last-Modified header is needed for + certain use cases. Bringing it back only for external requests fixes + these, while keeping the performance gain for checkout / update. + Votes: + +1: jcorvel, brane + +------------------------------------------------------------------------ </pre> <p>Further changes currently under consideration are listed in each release line's