You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by ps...@apache.org on 2026/08/27 11:30:16 UTC

(opendal-ofs) branch managed-v0/acceptance updated (b755379 -> 367b5f4)

This is an automated email from the ASF dual-hosted git repository.

PsiACE pushed a change to branch managed-v0/acceptance
in repository https://gitbox.apache.org/repos/asf/opendal-ofs.git


    omit b755379  test(harness): calibrate trusted file changes
    omit b19106d  build: scope TOML formatting to repository inputs
    omit 9d52b08  fix(harness): bind fixture storage to acceptance run
    omit bb2f508  test(harness): calibrate sparse large-file publication
    omit 06a20c0  fix(harness): keep product work on persistent storage
    omit 9bf98d5  fix(harness): place scale data on persistent storage
    omit 31b57d0  test(harness): report computed storage shape
    omit 647fba1  test(harness): add profile-driven managed acceptance
    omit 30b743e  feat(cli): expose managed volume workflows
    omit d2bab9e  feat(sync): reconcile and recover replica convergence
    omit 27e66f0  feat(sync): publish local replica changes
    omit 6197b56  feat(sync): restore managed replicas
    omit da30877  feat(sync): add replica request and state contracts
    omit caff9ef  feat(core): add managed object collection
    omit 03d0e58  feat(core): add managed volume state machine
    omit a6065ce  feat(core): add managed authority access
    omit 3ca0a03  feat(core): add managed file data pipeline
    omit 6e2c359  feat(core): add managed data segments
    omit 7c3f3fa  feat(core): add managed object storage substrate
     add f2eca96  docs: specify managed v0 storage format
     add a6843f1  feat(core): add managed object storage substrate
     add 64be3ad  feat(core): add managed data segments
     add 74f7114  feat(core): add managed file data pipeline
     add da38087  feat(core): add managed authority access
     add cdb8a98  feat(core): add managed volume state machine
     add 29a9e75  feat(core): add managed object collection
     add 7ec87b5  feat(sync): add replica request and state contracts
     add 5568cb8  feat(sync): restore managed replicas
     add 85546aa  feat(sync): publish local replica changes
     add d27d39f  feat(sync): reconcile and recover replica convergence
     add 097da21  feat(cli): expose managed volume workflows
     add 384ba6f  test(harness): add profile-driven managed acceptance
     add 9461f1b  test(harness): report computed storage shape
     add b47e4ae  fix(harness): place scale data on persistent storage
     add 50b720d  fix(harness): keep product work on persistent storage
     add 3e2690e  test(harness): calibrate sparse large-file publication
     add 06ab700  fix(harness): bind fixture storage to acceptance run
     add 29e3c4a  build: scope TOML formatting to repository inputs
     add 367b5f4  test(harness): calibrate trusted file changes

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (b755379)
            \
             N -- N -- N   refs/heads/managed-v0/acceptance (367b5f4)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 rfcs/0029_managed_format_v0.md | 848 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 848 insertions(+)
 create mode 100644 rfcs/0029_managed_format_v0.md