Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document database migration process for schema releases #304

Open
3 tasks
Shalsh23 opened this issue Sep 12, 2023 · 16 comments · May be fixed by #306
Open
3 tasks

Document database migration process for schema releases #304

Shalsh23 opened this issue Sep 12, 2023 · 16 comments · May be fixed by #306
Assignees
Labels
documentation Improvements or additions to documentation squad:release-management X SMALL Less than 1 day

Comments

@Shalsh23
Copy link

Shalsh23 commented Sep 12, 2023

  • Complete documentation for migration process as executed for the most recent migration (v7.7.2 to v7.8.0) @eecavanna
  • Links to any previous migration materials
  • Decide the best place to live for these and future such documentations

@eecavanna on September 29, 2024: New scope of task is in this comment. The above scope is obsolete (although it was accurate when written).

@Shalsh23 Shalsh23 added documentation Improvements or additions to documentation decision needed tag issues that need to be unblocked by decisions labels Sep 12, 2023
@eecavanna
Copy link
Collaborator

Thanks for creating this ticket, @Shalsh23! I'll do item 1 (and I'll do item 2 as part of that). For item 3, I'll eventually create a PR containing the document at some path, which we can change before merging.

@eecavanna
Copy link
Collaborator

I expect to finish item 1 this afternoon (Monday).

@eecavanna eecavanna linked a pull request Sep 19, 2023 that will close this issue
@ssarrafan
Copy link

I'm adding this issue to the sprint board for this sprint. If you're not planning to work on it this or next week let me know.

@eecavanna
Copy link
Collaborator

This has been a bit of a moving target, since the procedure being documented underwent some streamlining (changes) during the documentation process. I am still working on it, though.

@ssarrafan
Copy link

Not updated in the last 2 weeks. Removing from sprint and adding backlog label.

1 similar comment
@ssarrafan
Copy link

Not updated in the last 2 weeks. Removing from sprint and adding backlog label.

@ssarrafan ssarrafan added the backlog Not assigned to a sprint or not completed during a planned sprint. Needs to be reprioritized. label Nov 3, 2023
@ssarrafan
Copy link

Appears to be in progress. Will move to new sprint. @eecavanna let me know if this should be in the backlog.

@ssarrafan ssarrafan removed the backlog Not assigned to a sprint or not completed during a planned sprint. Needs to be reprioritized. label Dec 15, 2023
@eecavanna
Copy link
Collaborator

Thanks for moving it. I'm "actively" working on it (between the more urgent things that arise).

@ssarrafan
Copy link

@eecavanna @Shalsh23
removing this so I can close the previous sprint, adding backlog label
please add to current sprint if you're planning to work on it

@ssarrafan ssarrafan added the backlog Not assigned to a sprint or not completed during a planned sprint. Needs to be reprioritized. label Jan 2, 2024
@eecavanna
Copy link
Collaborator

I'm changing the "Definition of Done" for this ticket, to:

  • Document the migration process as of September 30, 2024

@eecavanna
Copy link
Collaborator

Removing @Shalsh23 from the assignee list. Thanks, @Shalsh23, for creating this ticket and documenting its initial scope!

@eecavanna eecavanna added X SMALL Less than 1 day squad:release-management and removed backlog Not assigned to a sprint or not completed during a planned sprint. Needs to be reprioritized. decision needed tag issues that need to be unblocked by decisions labels Sep 29, 2024
@ssarrafan
Copy link

@eecavanna can this one be closed yet?

@eecavanna
Copy link
Collaborator

I'm actively working on this one. It is not done yet (been lowering its priority in favor of Berkeley Schema Roll Out stuff, so am not as far along as I had expected by now). I'd prefer to leave it in the current sprint and I move it to the next sprint (or close, if finished) at the end of the day tomorrow.

@eecavanna
Copy link
Collaborator

I'll be working on this between now and the retreat. I'll go ahead and move it to next sprint because I don't think I'll finish it before then.

@eecavanna
Copy link
Collaborator

A couple team members have requested that the documentation include guidance on how to test a migrator, using a real Mongo database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation squad:release-management X SMALL Less than 1 day
Projects
Status: In Progress
3 participants