add doc about incompatible changes due to leasedb #2042
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2042
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some garbage collection options and some fields in responses to JSON stats queries were dropped for simplicity in the leasedb/cloud branch. Document these.
See https://github.com/tahoe-lafs/tahoe-lafs/commit/dbd6321f3756165eb32b5dfda6f8e4bf23a8105d.
... and https://github.com/tahoe-lafs/tahoe-lafs/commit/79e4766b2275c17620dc00053481e367a10c2fc7, but documentation for that was already updated in the same commit. (It assumes leasedb will be landed in v1.11.0 though, which is wrong.)
Replying to daira:
This is fixed in https://github.com/tahoe-lafs/tahoe-lafs/commit/1cddcb6bc33cfc2bfc238c64e5e0fc86a698c5b1.
The stats response is only documented in the source here, and it mentions the dropped fields, so there is nothing more to do here.
Milestone renamed
renaming milestone