Fediversity/meta
13
2
Fork 4
Code Issues1 Pull requests1 Projects Releases Packages Wiki Activity

WIP: data migration notes #29

Draft
kiara wants to merge 3 commits from data-model into main
Conversation 0 Commits 3 Files changed 2 +42 -73
kiara commented 2025-04-08 17:04:56 +02:00
Owner
No description provided.
kiara added 3 commits 2025-04-08 17:04:57 +02:00
fricklerhandwerk reviewed 2025-04-14 08:46:43 +02:00
architecture-docs/data-model-requirements.md
@ -5,0 +7,4 @@
Assumptions:
* Our deployment fully controls all versions, bypassing concerns on version mismatches.
fricklerhandwerk commented 2025-04-14 08:46:43 +02:00
Owner

I'm not sure what this means. The text you commented out describes the transfer between providers, and a different provider may simply have a different release of Fediversity deployed. While this may be a future-me sort of problem, depending on the release cadence and upgrade adoption delay by providers it may not be all that likely that two providers run the exact same release, and we need to at least to take that into account. The minimum that should happen initially is providing a UI for the case where two providers don't have the same version even if nothing can be done about it, and then keep at the back of our heads a user story for migrating and at the same time bumping the release, or something like that.

I'm not sure what this means. The text you commented out describes the transfer between providers, and a different provider may simply have a different release of Fediversity deployed. While this may be a future-me sort of problem, depending on the release cadence and upgrade adoption delay by providers it may not be all that likely that two providers run the exact same release, and we need to at least to take that into account. The minimum that should happen initially is providing a UI for the case where two providers don't have the same version even if nothing can be done about it, and then keep at the back of our heads a user story for migrating and at the same time bumping the release, or something like that.
kiara commented 2025-04-14 10:45:04 +02:00
Author
Owner

agree, c.f.

agree, c.f. https://git.fediversity.eu/Fediversity/Fediversity/issues/100#issuecomment-4598
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin data-model:data-model
git checkout data-model

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff data-model
git checkout data-model
git rebase main
git checkout main
git merge --ff-only data-model
git checkout data-model
git rebase main
git checkout main
git merge --no-ff data-model
git checkout main
git merge --squash data-model
git checkout main
git merge --ff-only data-model
git checkout main
git merge data-model
git push origin main
Sign in to join this conversation.
No reviewers
No labels
WP2
WP3
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Fediversity/meta#29
No description provided.
Delete branch "data-model"

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?