Julian Foad wrote on Wed, Mar 02, 2022 at 13:35:06 +0000: > On Feb 25 2022, Daniel Shahaf wrote: > >> [...] we are now deliberately choosing compatibility as the default, > > > > OK. However, in this case we should document this explicitly, since the > > book explicitly documents that «svn upgrade» would upgrade to the "most > > recent metadata format supported by your version of Subversion" > > (https://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.upgrade.html). > > > > I've grepped the book for «upgrade<» and I believe the only other place > > there we need to update is > > https://svnbook.red-bean.com/nightly/en/svn.ref.svnadmin.c.upgrade.html, > > to highlight the distinction. > > > > A release notes entry would be higher priority than updating the book. > > Documented in the help text of 'checkout' and 'upgrade', in r1898527, > like this for 'upgrade' and similar for 'checkout': > > [[[ > By default Subversion will upgrade the working copy to a version > compatible with Subversion 1.8 and newer.
Are we assuming that future minor versions (1.16, 1.17, etc.) will all continue to be able to read/write f31? This seems to be implied by the language here, and by the "and newer" language in `svn --version` [1]. I'm not proposing that we promise all 1.x versions will be able to read/write f31; I'm just confirming whether we realistically expect that to be the case. Cheers, Daniel [1] https://mail-archives.apache.org/mod_mbox/subversion-dev/202202.mbox/%3C9C7A3A8F-B5B0-46CF-9254-00811ADB201C%40getmailspring.com%3E > To upgrade to a different > version, use an option such as '--compatible-version=1.15'. > The versions available are the same as in the 'checkout' command. > Use 'svn --version' to see the compatible versions supported. > ]]] > > - Julian >
