Change package name for 1.0 release
runningcode opened this issue · 3 comments
Since flow 1.0 is a major update from 0.X should we change the package name?
Normally this policy is for major version upgrades, but does this also make sense for the 1.0?
Reasoning and rationale for changing package name and maven id:
http://jakewharton.com/java-interoperability-policy-for-major-version-updates/
I'm in the middle of migrating some flow+mortar code right now. Releasing 1.0 as a separate package would make things a hell of a lot nicer since I could elect to migrate portions of my app as needed. Essentially, it's much easier to start off with a cleanroom activity and add flow 1.0 than it is to take an old flow+mortar style setup and force it all into the new world at once.
When will be flow 1.0 stable version will be released ? Is this project still on progress?
We probably should, yeah.