cloud backend: prepare branch for LeastAuthority #2237
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2237
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?
This will be the branch that new customers of LeastAuthority's S4 product use. I want it to be separate from the 1819-cloud-merge branch (since that one is to be merged to Tahoe trunk which entails different stability requirements), but still in the tahoe-lafs github account.
(https://github.com/tahoe-lafs/tahoe-lafs/commits/2237-cloud-backend-s4)
(currently identical to 1819-cloud-merge)
I rebased this branch to trunk at https://github.com/tahoe-lafs/tahoe-lafs/commits/2237.cloud-backend-s4.1. This has lots of (hopefully shallow) test failures; Least Authority should continue to use 2237-cloud-backend-s4 for now.
thanks! I'll study the new branch.
The 2237-cloud-backend-s4 branch is currently failing with this error:
I intend to rebase it to be up-to-date with the 1.11.0 release — which will also make it possible to land it soon.
The current branch is https://github.com/tahoe-lafs/tahoe-lafs/commits/2237.cloud-backend-s4.3.
Oops now the current branch is 2237.cloud-backend-merge.0
It is a very large branch. The plan which has been discussed regarding it is to incrementally select self-contained portions of it to be worked on, reviewed, completed, and merged into master separately (ie, in their own feature branches) and then rebase what remains of 2237.cloud-backend-merge.0 onto the new master, reducing the overall size of 2237.cloud-backend-merge.0. In this way, it is hoped that each piece can be given the attention it requires while the quantity of remaining work is gradually reduced to something manageable.
Ha ha. Actually, 2237.cloud-backend-s4-merged.4.
I'm going to delete the rest of the branches from the tahoe-lafs org repo and update this ticket to reflect the fact that all efforts are currently centered on this branch. I'm also going to close at least a couple other tickets having to do with related work but which aren't obviously going to be resolved independently.
Least Authority is no longer pursuing this line of development.