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 3.1.0.1 #413

Closed
2 tasks done
kazu-yamamoto opened this issue Jun 13, 2019 · 7 comments
Closed
2 tasks done

Releasing 3.1.0.1 #413

kazu-yamamoto opened this issue Jun 13, 2019 · 7 comments
Assignees

Comments

@kazu-yamamoto
Copy link
Collaborator

  • changelog
  • ver bumps

I think we are ready.

@eborden
Copy link
Collaborator

eborden commented Jun 13, 2019

I'll get on this later today. We should probably think about setting up a release cadence. Once every 3 months?

@kazu-yamamoto
Copy link
Collaborator Author

I'm not sure. It's up to you. :-)

@kazu-yamamoto
Copy link
Collaborator Author

BTW, I would like to discuss what features should be included in v4. For instance, better errors.

@eborden
Copy link
Collaborator

eborden commented Jun 20, 2019

3.1.01 has been released on hackage: http://hackage.haskell.org/package/network-3.1.0.1

Cafe message sent:

Hello,

I'm happy to announce the release of network-3.1.0.1. This release includes
a few maintenance changes.

http://hackage.haskell.org/package/network-3.1.0.1

Contributors

Changes

You can view the changes on github.

https://github.com/haskell/network/releases/tag/v3.1.0.1

Thank you to network's contributors for their continued support.

@eborden eborden closed this as completed Jun 20, 2019
@eborden
Copy link
Collaborator

eborden commented Jun 20, 2019

@kazu-yamamoto I've started a project for 4.0.0.0. We can queue up proposed issues for that project there.

https://github.com/haskell/network/projects/3

@eborden
Copy link
Collaborator

eborden commented Jun 20, 2019

@maoe
Copy link
Member

maoe commented Jun 20, 2019

Maybe it's too late but I think both of #410 and #411 are silent breaking changes which are worth a major version bump. See the decision tree in PVP. I think both changes are yes on the second box.

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

3 participants