Skip to content

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

Description

@StachuDotNet

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    laterLet's think about this later -- we have some higher-priority things to work through first

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions