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

Help reviewing remaining PRs for 0.9.1 #725

Closed
12 tasks done
mmarchini opened this issue Jun 5, 2019 · 12 comments
Closed
12 tasks done

Help reviewing remaining PRs for 0.9.1 #725

mmarchini opened this issue Jun 5, 2019 · 12 comments

Comments

@mmarchini
Copy link
Contributor

mmarchini commented Jun 5, 2019

We had a lot of changes since 0.9.0 came out, and all issues we have on 0.9.1 milestone have a Pull Request open. I would like to merge these soon so we can release 0.9.1 and start focusing on 0.9.2.

These are the PRs I have in mind so far:

If folks could help reviewing those PRs, that would be awesome.

Also, if there are other PRs folks believe should go in our next release, please comment here so we can decide if it should be included or not. I would like to avoid merging big or impactful changes before we release 0.9.1 (especially #535, #667 and #711) since it would be nice to have those changes in master for a few weeks before they make into a release.

@danobi
Copy link
Member

danobi commented Jun 5, 2019

I volunteer #623 to be included :)

@danobi
Copy link
Member

danobi commented Jun 5, 2019

I can help review some stuff.

@mmarchini
Copy link
Contributor Author

I volunteer #623 to be included :)

Makes sense, and doesn't look like something risky to have in the next release. I'll add to the list :)

@mmarchini
Copy link
Contributor Author

Should we include #714? On one hand it fixes two issues, on the other hand I'm worried of having it in a release without having it on master for some time first.

@danobi
Copy link
Member

danobi commented Jun 6, 2019

I think it should bake in master a bit. I don't think it's a critical bug.

@mmarchini
Copy link
Contributor Author

I'll add #732 since several users are facing this issue.

@mmarchini
Copy link
Contributor Author

Also adding #762 because it fixes a critical issue with ntop.

@danobi
Copy link
Member

danobi commented Jun 12, 2019

Should we cut release branches instead of doing version-freeze tags on PRs?

@mmarchini
Copy link
Contributor Author

Yes, that would be better.

@mmarchini
Copy link
Contributor Author

mmarchini commented Jun 17, 2019

I'm writing the changelog for 0.9.1 now. I think maybe #742 should be included as well, otherwise we'll introduce a breaking change in this version (disallow optional positional parameters) just to revert to the old behavior in the next version.

@ajor
Copy link
Member

ajor commented Jun 23, 2019

All PRs merged!

@mmarchini
Copy link
Contributor Author

v0.9.1 was released today, so I'll close this issue.

Thank you for everyone who helped with reviews and pull requests!

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