You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "Xuanwo (via GitHub)" <gi...@apache.org> on 2026/10/26 06:09:02 UTC
[I] Tracking: YinYang implementation roadmap and release readiness [opendal-yinyang]
Xuanwo opened a new issue, #67:
URL: https://github.com/apache/opendal-yinyang/issues/67
# YinYang implementation roadmap
Deliver a usable Managed filesystem combination first, complete Managed synchronization and native platform coverage next, and qualify additional models and persistent contracts for release.
## Baseline
Verified on 2026-10-26 against main `1146781a127a7fa3ad2afee3e3ca8c823d659013`. PRs #59–#65 are merged. The core, both publication authorities, recoverable handles, shared Mount state, baseline-bound Sync content edits, native bridge and macOS prototypes exist experimentally. Native evidence covers selected isolated macOS flows, not production support.
| Product combination | Current state |
| --- | --- |
| Managed Mount | Shared runtime and FSKit prototype; external EOF coherence and application acceptance remain open. |
| Managed Sync | Existing-file content coordination and File Provider prototype; full namespace and ordinary-directory reconciliation remain open. |
| Direct Mount | Not implemented in the current architecture. |
| Direct Sync | Not implemented. |
## Milestones
### M1 — A usable macOS Managed combination
Close the FSKit coherence gap, validate real application/failure behavior and provide a coherent volume lifecycle. File Provider remains bounded by its advertised capabilities; namespace-dependent safe-save belongs to M2.
### M2 — Complete Managed behavior and validate native platforms
Add namespace coordination, ordinary-directory Sync and explicit conflict/status workflows. Validate Linux and Windows lifecycle contracts before freezing shared interfaces; these probes can start before M1 finishes.
### M3 — Broaden coverage and qualify stable contracts
Build Direct read-only access before conditional writes and Sync. Establish cost evidence, interoperability/version rules and release qualification. A release advertises only combinations that pass their own gates; all four product quadrants need not ship together.
### Parallel work
CLI historical restore and durable directory publication recovery can proceed independently. Reconcile maintained project documentation with the merged state.
## Tracking and completion policy
The child tasks below carry scope, acceptance and dependencies. Completion requires the observable outcome and its evidence, not merely a merged PR or a started build. Dates here are state snapshots, not delivery deadlines; no ownership or release commitment is assigned.
#19 remains the architecture-direction index. This issue is the implementation roadmap. #26 is the historical umbrella whose body explicitly says it is not intended to merge.
Garbage collection, retention expiry, compression, encryption, hard links and ACL/xattr require separately scoped contracts. Windows Cloud Files follows Sync maturity and a separate frontend decision. Neither is silently included in the first usable combination.
## Sources
- [Current specifications](https://github.com/apache/opendal-yinyang/tree/1146781a127a7fa3ad2afee3e3ca8c823d659013/specs)
- [macOS support and acceptance boundaries](https://github.com/apache/opendal-yinyang/blob/1146781a127a7fa3ad2afee3e3ca8c823d659013/specs/macos-frontends.md)
- [Architecture direction](https://github.com/apache/opendal-yinyang/blob/main/rfcs/0016_filesystem_architecture.md)
## Implementation tasks
The linked child issues are being registered as part of this roadmap update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org