In #1196 (comment) we agreed to group all pre-v1 DB migration operations into a single migration step.
Doing this will minimize startup time cost for new clusters. If we don't do it, the startup code for new clusters will be slower ~forever (unless we get really creative in how we manage migration scripts, which is not planned, and which caries it's own risks).
We should do this just prior to releasing v1 since we anticipate that additional DB migration scripts will be added between now and then.
Julian Gutierrez Oschmann (@juli4n) Jeremy Alvis (@iplay88keys) Benjamin Elder (@BenTheElder) Tim Hockin (@thockin)
In #1196 (comment) we agreed to group all pre-v1 DB migration operations into a single migration step.
Doing this will minimize startup time cost for new clusters. If we don't do it, the startup code for new clusters will be slower ~forever (unless we get really creative in how we manage migration scripts, which is not planned, and which caries it's own risks).
We should do this just prior to releasing v1 since we anticipate that additional DB migration scripts will be added between now and then.
Julian Gutierrez Oschmann (@juli4n) Jeremy Alvis (@iplay88keys) Benjamin Elder (@BenTheElder) Tim Hockin (@thockin)