You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by xu...@apache.org on 2026/10/26 16:23:56 UTC

(opendal-yinyang) branch xuanwo/managed-sync-status-docs updated: docs: link Linux acceptance evidence and historical umbrella

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

Xuanwo pushed a commit to branch xuanwo/managed-sync-status-docs
in repository https://gitbox.apache.org/repos/asf/opendal-yinyang.git


The following commit(s) were added to refs/heads/xuanwo/managed-sync-status-docs by this push:
     new 3a07a26  docs: link Linux acceptance evidence and historical umbrella
3a07a26 is described below

commit 3a07a2680e5171b66361d1ed2bef87c45a294e16
Author: Xuanwo <gi...@xuanwo.io>
AuthorDate: Tue Oct 27 00:23:46 2026 +0800

    docs: link Linux acceptance evidence and historical umbrella
    
    Link the accepted Linux FUSE PRs, bound native validation to the AWS ledger and GitHub run, and identify the closed historical umbrella as non-mergeable.
    
    Co-authored-by: Chojan Shang <ps...@apache.org>
---
 README.md       | 20 ++++++++++++++------
 specs/README.md | 14 +++++++++-----
 2 files changed, 23 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 9288f18..b2b886a 100644
--- a/README.md
+++ b/README.md
@@ -29,12 +29,17 @@ Apache OpenDALâ„¢ YinYang is a cross-platform filesystem foundation.
 ## Current support
 
 - **Managed Mount:** The experimental Linux FUSE frontend supports read-only and
-  writable configurations through `yy --volume CONFIG mount MOUNTPOINT`. PRs
-  #83, #84, and #85 added the frontend, writable callbacks, and native
-  acceptance on 2026-10-27. All 22 real-mount scenarios passed on an isolated
-  Ubuntu 24.04 AWS host and in GitHub Linux CI, covering both publication
-  authorities, saves, failure retention, refresh, crash recovery, and teardown.
-  See the [frontend contract](specs/linux-fuse.md) and
+  writable configurations through `yy --volume CONFIG mount MOUNTPOINT`.
+  [PR #83](https://github.com/apache/opendal-yinyang/pull/83),
+  [PR #84](https://github.com/apache/opendal-yinyang/pull/84), and
+  [PR #85](https://github.com/apache/opendal-yinyang/pull/85) added the
+  frontend, writable callbacks, and native acceptance on 2026-10-27. The
+  [PR #85 record](https://github.com/apache/opendal-yinyang/pull/85) documents
+  all 22 real-mount scenarios passing on an isolated Ubuntu 24.04 AWS host;
+  the [GitHub Linux FUSE job](https://github.com/apache/opendal-yinyang/actions/runs/40312762537/job/121539655561)
+  also passed all 22. Both publication authorities are exercised, covering
+  saves, failure retention, refresh, crash recovery, and teardown. See the
+  [frontend contract](specs/linux-fuse.md) and
   [acceptance guide](docs/linux-fuse-acceptance.md). This is experimental
   native validation, not release support.
 - **Managed Sync:** The [Sync runtime](specs/sync-runtime.md) coordinates pinned
@@ -50,6 +55,9 @@ Apache OpenDALâ„¢ YinYang is a cross-platform filesystem foundation.
 
 The [implementation roadmap](https://github.com/apache/opendal-yinyang/issues/67)
 tracks the remaining integration and platform work.
+The closed historical umbrella
+[PR #26](https://github.com/apache/opendal-yinyang/pull/26) explicitly was not
+intended to merge and is not the active implementation stack.
 
 ## Publish and restore a directory
 
diff --git a/specs/README.md b/specs/README.md
index b8797c7..7a9e6e9 100644
--- a/specs/README.md
+++ b/specs/README.md
@@ -22,11 +22,15 @@ invariants, compatibility rules, and implementation boundaries. Specifications
 evolve with the implementation and must be updated in the same change as the
 contract they describe.
 
-On 2026-10-27, PRs #83, #84, and #85 established the Linux Managed Mount and
-its native acceptance suite. All 22 real-mount scenarios passed on an isolated
-Ubuntu 24.04 AWS host and in GitHub Linux CI, using both publication
-authorities. See the [acceptance guide](../docs/linux-fuse-acceptance.md). This
-evidence does not make the frontend a release-supported combination.
+On 2026-10-27,
+[PR #83](https://github.com/apache/opendal-yinyang/pull/83),
+[PR #84](https://github.com/apache/opendal-yinyang/pull/84), and
+[PR #85](https://github.com/apache/opendal-yinyang/pull/85) established the
+Linux Managed Mount and its native acceptance suite. All 22 real-mount
+scenarios passed on an isolated Ubuntu 24.04 AWS host and in GitHub Linux CI,
+using both publication authorities. See the
+[acceptance guide](../docs/linux-fuse-acceptance.md). This evidence does not
+make the frontend a release-supported combination.
 
 The transactional filesystem specification is an explicit design-ahead
 exception. It defines the replacement contract without requiring compatibility