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

Goal: Reach Feature Parity with Dark-Classic, and Migrate User Canvases #5309

Open
13 tasks
StachuDotNet opened this issue Feb 19, 2024 · 0 comments
Open
13 tasks
Labels
later Let's think about this later -- we have some higher-priority things to work through first

Comments

@StachuDotNet
Copy link
Member

StachuDotNet commented Feb 19, 2024

This issue aims to

  • cover the general topic of "when can users port their canvases from dark-classic to dark-next?"
  • and outline the migration process, of our users' code from -classic to -next.

We're a few months away from migrating any user code to -next, but here's a rough sketch in the meantime:

  • bring back cloud runtime
  • secrets
  • static assets
  • http handlers
  • user dbs
  • decent editor
  • crons
  • workers
  • announce various migrations - blog, email to users w/ running canvases, etc
  • code to migrate stuff
  • opt-in phase
  • migrate the rest
  • shutdown-classic
@StachuDotNet StachuDotNet added the needs-review I plan on going through each of the issues and clarifying them -- this is to mark remaining issues label Feb 19, 2024
@StachuDotNet StachuDotNet added later Let's think about this later -- we have some higher-priority things to work through first and removed needs-review I plan on going through each of the issues and clarifying them -- this is to mark remaining issues labels Jun 25, 2024
@StachuDotNet StachuDotNet changed the title Component: Reaching Feature Parity with Dark-Classic Goal: Reach Feature Parity with Dark-Classic, and Migrate User Canvases Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
later Let's think about this later -- we have some higher-priority things to work through first
Projects
None yet
Development

No branches or pull requests

1 participant