Prepare new release (2.1.0)?#1764
Merged
Merged
Conversation
Contributor
|
2.1.0 is a little overdue so I'm 👍. I'll review the PRs you listed and provide feedback again just to be safe (in case I missed any of them). |
Contributor
|
I would say "definitely" #1766. That shouldn't be a "maybe" |
Contributor
|
Looking over the PRs listed above now:
|
Contributor
|
Updated to inclue #1768 which is a 👍 merge it. |
|
I don't want to be pushy, but I'm very excited for 2.1 😄 The pending 2.x SNI stuff is huge for us. If I can help with the release at all, let me know! |
kennethreitz
added a commit
that referenced
this pull request
Dec 4, 2013
Prepare new release (2.1.0)?
Contributor
|
@kennethreitz this PR wasn't finished. There's still stuff missing from the Changelog |
Contributor
|
@sigmavirus24 d'oh, sorry guys. I got ahead of myself :) Hoping to do this release tonight. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are a few nasty bugs that we've fixed since the last release, including the broken SNI support. It'd be good to get another release out. I think a few things have changed dramatically enough that this is probably a minor release (e.g. takes us to 2.1.0). Thoughts? /cc @kennethreitz @sigmavirus24
Still to do:
Fixed #1711 #1713, Honor session hooks #1657, Unencode usernames and passwords taken from URLs. #1768, and Quote qop values in digest auth. #1766; maybe Fix for #1728 #1729, Update host header on redirect. #1628 and Separate connect timeouts #1743 depending on how @kennethreitz feels).If nothing else Runscope could do with this release, so it'd be nice to be in good shape.