-
Notifications
You must be signed in to change notification settings - Fork 136
[PULP-220] Purge migrations #6110
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
Conversation
6e6a7d9 to
c7f0df2
Compare
c7f0df2 to
c34a597
Compare
|
Is this really a 3.70 blocker? I thought we'd talked about not doing too many changes at once in this area for 3.70? |
|
I probably would not drop the old migrations until at least after we've done so for the plugins. |
|
No not necessarily a blocker. But this is the change, why we request all plugins to rebase their migrations. |
|
@mdellweg Can this proceed now? |
It can proceed any time. The question is when do we want to take the risk? |
|
I think we should do it |
|
Well anytime is not exactly right. We must align it with a breaking change release. |
c34a597 to
ecaa9ee
Compare
|
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution! |
6c5a341 to
cba3e2c
Compare
cba3e2c to
06ffad9
Compare
06ffad9 to
cbf2091
Compare
cbf2091 to
91b4987
Compare
No description provided.