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

Tracking issue for libz blitz evaluation of walkdir #47

Closed
22 tasks done
KodrAus opened this issue Jun 14, 2017 · 3 comments
Closed
22 tasks done

Tracking issue for libz blitz evaluation of walkdir #47

KodrAus opened this issue Jun 14, 2017 · 3 comments

Comments

@KodrAus
Copy link
Contributor Author

KodrAus commented Jun 26, 2017

I've added some PRs to a list of non-breaking changes so we can look at merging those in and doing a point-release before 2.0.

I'm not sure what strategy you had @BurntSushi for splitting the changes between breaking and non-breaking. Maybe we can do some git flow by making a 1.x branch and merge the non-breaking changes into that.

EDIT: Alternatively we could just not worry about breaking/non-breaking and pool everything up for 2.0.

@BurntSushi
Copy link
Owner

EDIT: Alternatively we could just not worry about breaking/non-breaking and pool everything up for 2.0.

Yes, I'd prefer this route. Let's not do more work than we need to. :-)

If need be, we can branch off of the 1.0.7 tag (which is currently the most recent release of 1.x) in the future if we need or want to backport any fixes from 2.x.

@KodrAus
Copy link
Contributor Author

KodrAus commented Jul 12, 2017

I've updated the OP, looks like we've got open PRs for all issues except #54, and more design work in #53 🎉 Awesome work everyone and thanks for contributing!

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