You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@subversion.apache.org by "Julian Foad (Jira)" <ji...@apache.org> on 2022/02/24 12:21:00 UTC

[jira] [Assigned] (SVN-4883) multi-wc-format

     [ https://issues.apache.org/jira/browse/SVN-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Foad reassigned SVN-4883:
--------------------------------

    Assignee: Julian Foad

> multi-wc-format
> ---------------
>
>                 Key: SVN-4883
>                 URL: https://issues.apache.org/jira/browse/SVN-4883
>             Project: Subversion
>          Issue Type: Improvement
>    Affects Versions: 1.14.0
>            Reporter: Julian Foad
>            Assignee: Julian Foad
>            Priority: Major
>
> Allow a new version of the Subversion client to work on a WC that uses an older format, without upgrading that WC to the newest format the client knows.
> Concrete example (currently hypothetical):
>  * if a v1.15 client were to support this feature, it could be made compatible with both the WC format used from Subversion 1.8 to 1.14 ("WC format 31") and a new format that would be introduced at the same time in 1.15 ("WC format 32").
> This will allow the user to:
>  * use the new client and an old client against the same (old-format) WC
>  * use the new client's new features with a (new-format) WC
> An implementation of this was recently merged into trunk. It was was developed on a branch named 'multi-wc-format'.
> UI exposure of this feature includes:
>  * 'svn checkout' and 'svn upgrade' default to the oldest compatible WC format.
>  * 'svn checkout' and 'svn upgrade' accept an option such as '--compatible-version=1.15' to request a newer format.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)