Preparing for ember-redux v3.0.0

As we upgrade to babel 6 the ember-redux-shim dependency will bump to a new major version because it will now require transform-object-rest-spread

While I’m waiting to merge this related addon I thought we could discuss a few changes as we make our way toward the next major release.

The intimate apis handleChange and getAttrs will both go away (they have deprecation warnings right now). With some discussion it seems we should also add a deprecation to the non combineReducers implementation we supported until recently and remove this completely in the next major release.

The RFC @brettburley has up to move the connect/and route imports may be a great candidate (we could add a deprecation warning to make people aware of this and it would likely remain until the v4 version as I hate to break people with a ton of connect import statements). @brettburley you have a PR up for this but it may need a rebase/ and I wanted to see if you could add the deprecation warnings you mentioned (still exporting from the current connect/route locations)

The store extension stuff could use additional documentation and work (a few of us are still working through PR #121 and I’m sure this will work itself out in the next week or so).

Anything else we should be thinking of as we start preparing for another major version bump?

[toranb]

With the announcement of node 8 this past week, I think it’s fair to assume node 6+ as a build time dependency at some point in 2017. For now I’m planning to start work on the v3.0 release in July

[SlyDen]

My project is OK for Node 6+ (I’m on 7+ actually right now). in this case Node is a build dependency (not a runtime) and in most cases it shouldn’t be a problem for people to update their build pipeline.

I suspect there can be hard cases when somebody forced to stay on old Node, but they can stick to older release anyways.