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

Tag a new release? #168

Closed
EricForgy opened this issue Jan 23, 2018 · 5 comments
Closed

Tag a new release? #168

EricForgy opened this issue Jan 23, 2018 · 5 comments

Comments

@EricForgy
Copy link
Contributor

There has been a lot of progress with HTTP after merging #135 and some subsequent clean up.

Several people, e.g. myself, @oxinabox, @ararslan , etc, would like a tag so we can update our packages 😊

What is left to do before that can happen?

@quinnj
Copy link
Member

quinnj commented Jan 24, 2018

I'm going to make a big push on 0.7 compat tonight to get tests passing and there are a few deprecations to clean up (I have a couple changes locally). If things go smoothly, I think we should be ready for a tag tonight/tomorrow.

@samoconnor, anything else you're working on or want to get in before a new tag?

@ararslan
Copy link
Member

Anything else to do now that #171 has been merged?

@quinnj
Copy link
Member

quinnj commented Jan 25, 2018

I'm checking out HTTP dependencies tonight and hopefully won't run into too many unrelated compat problems trying to test if we've broken anything too badly.

@quinnj
Copy link
Member

quinnj commented Jan 25, 2018

ok, #175 is the last thing I want to get in before tagging, so pending good CI, I'll merge and tag. If anyone has other issues/concerns, speak now or..........wait till the next release!

@EricForgy
Copy link
Contributor Author

Yay! 🎉

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