Properly document DB changes and provide migrations for old version #241

Closed
driverdan opened this Issue May 14, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@driverdan

Apparently the newest version of subway is completely abandoning MongoDB in favor of sqlite. The documentation says nothing about this and provides no warning for existing users. There also doesn't appear to be any migration path.

Making major changes like this requires informing / warning users properly and adequate documentation.

@thedjpetersen

This comment has been minimized.

Show comment Hide comment
@thedjpetersen

thedjpetersen May 14, 2013

Owner

Sorry for the confusion. This ended up being decided in a separate issue( see here: #70 ). I am afraid there isn't any clear migration path.

Owner

thedjpetersen commented May 14, 2013

Sorry for the confusion. This ended up being decided in a separate issue( see here: #70 ). I am afraid there isn't any clear migration path.

@driverdan

This comment has been minimized.

Show comment Hide comment
@driverdan

driverdan May 14, 2013

Understood. The README should still include a section about breaking changes so users of older versions can know about it before upgrading.

Understood. The README should still include a section about breaking changes so users of older versions can know about it before upgrading.

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