-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
Some relevant links to potentially include in the documentation: |
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. |
I expect to finish item 1 this afternoon (Monday). |
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. |
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. |
Not updated in the last 2 weeks. Removing from sprint and adding backlog label. |
1 similar comment
Not updated in the last 2 weeks. Removing from sprint and adding backlog label. |
Appears to be in progress. Will move to new sprint. @eecavanna let me know if this should be in the backlog. |
Thanks for moving it. I'm "actively" working on it (between the more urgent things that arise). |
@eecavanna @Shalsh23 |
I'm changing the "Definition of Done" for this ticket, to:
|
@eecavanna can this one be closed yet? |
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. |
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. |
A couple team members have requested that the documentation include guidance on how to test a migrator, using a real Mongo database. |
@eecavanna on September 29, 2024: New scope of task is in this comment. The above scope is obsolete (although it was accurate when written).
The text was updated successfully, but these errors were encountered: