[scottcorgan]

You can follow along on the #elm-dev slack channel to know everything that's happening with the development with Elm. What 0.19 is going to include has been documented and made available to anyone that wants to know.

A long release cycle has meant I don't have to update any of my existing Elm code. That's a WIN to me! :)

[Tehnix]

> A long release cycle has meant I don't have to update any of my existing Elm code. That's a WIN to me! :)

Instead you'll get a very big batch of breaking changes, that means the community will properly take a very long time to migrate to 0.19. Long release cycles are NOT a good thing.

Python 3 is the canonical example, but there are plenty of other times where too big a release brings about splits in communities.

[Skinney]

You'll get a small batch of breaking changes, most of them will be automatically fixed by the elm-upgrade tool. The community will probably migrate to 0.19 faster than 0.18 or 0.17, which both had much more breaking changes than 0.19.

[scottcorgan]

Fair point. I think the Elm devs knew that, so they created https://github.com/avh4/elm-upgrade for the 0.17 to 0.18 upgrade. It's fixes _almost_ everything.

It will be updated for 0.19 as well!