On Wed, Apr 2, 2025 at 10:40 AM Daniel Sahlberg <daniel.l.sahlb...@gmail.com> wrote: > > Hi, > > I've been reviewing the 1.15 release notes on the staging site[1].
Thanks for doing that! > We need to complete the New Feature Compatibility Table ¶ > [[[ > New Feature Minimum Client^1 Minimum Server Minimum Repository Notes > Pristines On Demand 1.15 TODO TODO > Streamy Checkouts 1.15 TODO TODO > ]]] > > My understanding is that both the server version and the repository is irrelevant for both these changes. Is this correct? > > # Repository Access Comparison > [[[ > Command Normal Pristines On Demand > [...] > conflict resolving (resolve/merge/up/sw) Sometimes Sometimes (...) > ]]] > Why the ellipsis on POD? > > > The relase notes contain a referene to i525-user-guide.html (generated from /notes/i525-user-guide.md). I've reviewed this as well: > > The document seems to imply that it is possible to upgrade an existing WC from format 31 to format 32 and that it will immediately be converted to a "bare" wc. (With a TODO saying we "might split into two operations"). > > I can't find a reference in docs or code how to convert an existing wc to a "bare" wc. `svn upgrade --compatible-version=1.15` seems to keep the pristine files. I can't find an option to remove them. Am I missing something? Good catch! I think that text is based on earlier revisions of the feature. (The use of the word "bare" wc tells me that it was written back when we were still grappling with the terminology. At some point we stopped using "bare" wc to describe what is now called a pristines-on-demand WC.) Format 32 does *not* automatically imply pristines-on-demand--the i525 feature was never intended to eliminate or phase out pristine storage, but rather to make pristine storage optional by user request. I just checked and: Running 'svn upgrade --compatible-version=1.15' in a format 31 working copy produces a format 32 working copy with traditional full pristine storage, and: 'svn upgrade' does *not* accept the --store-pristine=no argument: $ svn upgrade --compatible-version=1.15 --store-pristine=no Subcommand 'upgrade' doesn't accept option '--store-pristine ARG' Type 'svn help upgrade' for usage. I think the plan was to add --store-pristine=yes/no capability to 'svn update' and 'svn upgrade' in the future. > I didn't look into all the TODOs but we can probably resolve most of them quite quick. I guess you mean the TODOs in the i525 user guide. (The draft release notes have only 5 TODOs, of which 4 are in the compatibility table and 1 is a reminder to link to the i525 user guide.) I haven't gone through the user guide yet but I'll try to do it soon. Cheers, Nathan
