You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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/
The text was updated successfully, but these errors were encountered: