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

Releasing a new version #52

Closed
mmzx opened this issue Feb 27, 2019 · 7 comments
Closed

Releasing a new version #52

mmzx opened this issue Feb 27, 2019 · 7 comments

Comments

@mmzx
Copy link
Collaborator

mmzx commented Feb 27, 2019

There are some reasons that would favor creating a new version:

What would you think about the new version to be 0.1.3.1 to make a minor version bump?

@mmzx
Copy link
Collaborator Author

mmzx commented Feb 27, 2019

@BurntSushi, currently you are the maintainer of this package according to the hackage database. If this issue was relevant could you please change the settings to make it possible to upload a new version to hackage?

@BurntSushi
Copy link
Owner

@mmzx I can change the settings sure. But I need to enter a user account for uploading new versions. What is your Hackage account username?

@mmzx
Copy link
Collaborator Author

mmzx commented Mar 23, 2019

@BurntSushi it is: mmzx .

@BurntSushi
Copy link
Owner

@mmzx Thanks. I've added you.

@mmzx
Copy link
Collaborator Author

mmzx commented Mar 25, 2019

Brilliant, thank you! Later today I will make the necessary action(s).
What do you think about v2.0.0.0, instead of 1.4.0.0? - there is a breaking change.

@BurntSushi
Copy link
Owner

If there's a breaking change, then do a major version bump.

@mmzx
Copy link
Collaborator Author

mmzx commented Mar 26, 2019

Thanks! 0.2.0.0 has been uploaded to hackage.

@mmzx mmzx closed this as completed Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants