Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change package name for 1.0 release #224

Open
runningcode opened this issue Jan 31, 2017 · 3 comments
Open

Change package name for 1.0 release #224

runningcode opened this issue Jan 31, 2017 · 3 comments
Labels
Milestone

Comments

@runningcode
Copy link
Contributor

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/

@dcow
Copy link
Contributor

dcow commented Feb 1, 2017

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.

@ye-lin-aung
Copy link

When will be flow 1.0 stable version will be released ? Is this project still on progress?

@loganj loganj added the API label Feb 13, 2017
@loganj loganj added this to the 1.0 release milestone Feb 13, 2017
@loganj
Copy link
Collaborator

loganj commented Feb 13, 2017

We probably should, yeah.

@loganj loganj changed the title Should we change flow package name for 1.0 release? Change package name for 1.0 release Feb 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants