kill main migrations

[rueckstiess]

They haven't been useful since 1.1.5 and are taking time to load on every upgrade.

If someone upgrades from 1.1.5 to 1.8, they will

• either lose their connections and privacy settings
• or have to install any version in between first to migrate, and then start 1.8.

I'm ok with this, given we even have a work-around.

[pzrq]

LGTM 👍

Compass 1.8.0-dev still starts as expected. Of 3 test runs on local at least one completely passed for me.

[satyasinha]

LGTM

[leafybot]

Yay!

…

On Wed, Mar 29, 2017 at 2:53 AM Satya Sinha ***@***.***> wrote: Merged #899 <#899>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#899 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AR0ozej__lbG2_nZp2j2DYrc18FnJzVCks5rqf_8gaJpZM4MsiLI> .

[pzrq]

For posterity, one reason it was decided to kill these main process migrations was that they would combine with the functional tests when you ran npm test -- --functional on a macOS machine. Specifically if you had also started a Compass v1.1.5 or earlier on the same machine, they would hang for 60 seconds generating the screenshot below (which affected my macOS box for nearly four months via #664). This is something which also never happens on Travis.

From my previous experience with Django unit testing and the community's response, I continue to strongly suggest the Compass Team follows the pattern that migrations should (as a general rule) be run all the time when running tests, so we would expect to run them on Travis and on localhost when running npm test. Plus they only took a second or two, unlike Django's SQL+ORM ones which can take minutes or even hours.

This also gave us this trigger to allow such a cleanup, which would most likely not otherwise have occurred until hypothetically in the very very long arc of time something like a new node version breaks AmpersandModel which would break these migrations and thus error, most likely in production only.

TL;DR: Migrations don't need to be forever.