nvrl/proton-drive-linux
1
0 Fork 0
mirror of https://github.com/narrrl/proton-drive-linux.git synced 2026-11-03 16:41:26 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: record the full a6f36d5 account run in the 3.0.0 status

Browse Source
This commit is contained in:
nvrl committed 2026-10-04 04:45:48 +02:00
1 parent 85e80d8aac
commit eb1c105bbf
1 file changed
+7 -4
Download Patch File Download Diff File Expand all files Collapse all files
docs/MILESTONE-3.0.0-STATUS.md
+7 -4
View File
@@ -49,10 +49,13 @@ Tracks `docs/MILESTONE-3.0.0.md`. Update it with every commit that moves a phase
run. run.
- [ ] Known-bug list in `sim/run.rs` is empty: B125 and B130 open; B129 and B132 fixed but - [ ] Known-bug list in `sim/run.rs` is empty: B125 and B130 open; B129 and B132 fixed but
unconfirmed. unconfirmed.
- [ ] A clean account run. The one on a6f36d5 (2026-10-04, LAN, partial report) failed only - [ ] A clean account run. The one on a6f36d5 (2026-10-04, LAN: 427 passed, 12 failed)
B113 and B121, on every on-demand mount. B121 was a bug (B149, fixed); B113's case failed B113 and B121 on every on-demand mount, two mirror-to-mirror move cases, and
still expected creates to reach Drive at once and now accepts queued ones. Not the journal check. B121 was a bug (B149, fixed); B113's case still expected creates
confirmed yet. to reach Drive at once and now accepts queued ones. The move cases were the harness:
it retried every source after one was busy, and expected a refusal where a mirror to
mirror move carries the local copy along. The journal showed a conflict copy retrying
into a deleted folder (B150, fixed). Not confirmed yet.
5. **Release**: 2.10.0 is tagged; the 2.9.0 tag still waits for the user's go-ahead. 5. **Release**: 2.10.0 is tagged; the 2.9.0 tag still waits for the user's go-ahead.
## After 3.0.0 ## After 3.0.0