mistercrunch commented on issue #29836: URL: https://github.com/apache/superset/issues/29836#issuecomment-2864076291
Wondering if there's a way to just fix the latest release so that you can migrate from anywhere to latest and future destinations. Maybe by using the branching features in alembic. I have to admit I'm still a little confused and that a graph diagram would really help here. Still unclear whether one of the migration is missing in some places, or whether it's just in a different order across releases. From my understanding alembic has support for some branching as long as you merge the branches. There's probably a way to fix this in `master` and future releases (?) Also trying to understand the population that's affected. Sounds like it's only affecting people who have migrated to people that followed a precise upgrade path? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
