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
KodrAus opened this Issue Jun 14, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@KodrAus

This comment has been minimized.

Show comment
Hide comment
@KodrAus

KodrAus Jun 26, 2017

Contributor

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.

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@BurntSushi

BurntSushi Jun 26, 2017

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.

Owner

BurntSushi commented Jun 26, 2017

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

This comment has been minimized.

Show comment
Hide comment
@KodrAus

KodrAus Jul 12, 2017

Contributor

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!

Contributor

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!

@killercup killercup referenced this issue Aug 1, 2017

Closed

August 2017 #35

10 of 10 tasks complete

@KodrAus KodrAus closed this Aug 4, 2017

@KodrAus KodrAus referenced this issue Aug 4, 2017

Closed

Release 2.0 on crates.io #79

2 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment