A status review from my P.O.V.
Pristines (#525):
* issues filed (potential blockers):
- #4888 authz denied during textbase sync
(an edge case issue, not sure if it's a blocker)
- #4889 per-WC config
(wanted)
- #4891 fix disabled tests
(a few different edge cases; much of the analysis is posted in the issue)
* next milestone: merge to trunk
- Are any of the issues blockers for merge to trunk? I would suggest not.
Getting multi-wc-format ready for release (#4883):
* issues filed (potential blockers):
- #4885 WC upgraded and not-upgraded notifications
(still open for some nice-to-haves, but probably done enough for MVP)
- #4886 config for default WC version for checkout & upgrade
()
- #4887 clarify/unify option names for compatible-version
(perhaps change '--compatible-version' to '--wc-compatible-version'
or '--min-compatible-client')
* not filed:
- API review; thread: "multi-wc-format review"
(state is APIs are mostly private and a bit messy; not clear what,
if anything, we would want to change)
Release notes are drafted:
<https://subversion-staging.apache.org/docs/release-notes/1.15#wc-upgrade>
<https://subversion-staging.apache.org/docs/release-notes/1.15#bare-working-copies>
Testing:
Some testing by devs has been done of both multi-wc-format and
pristines-on-demand. It seems to be generally in good shape; no glaring
issues found.
Next steps I suggest:
- propose merge to trunk
- review the issues mentioned: fix or decide to postpone each
- Julian
