-
Notifications
You must be signed in to change notification settings - Fork 97
fix!: drop support for Python 2.7 / 3.5 #212
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
Changes from 1 commit
21ac69a
78caa92
35c8216
35ba7d3
61490f5
74c6179
6e21b01
fe7d454
d77fbb0
440e571
90c1bd1
026ee31
4165633
ad7b40b
dbc234f
4d87012
c480784
72d175b
01b49c4
0f6a745
cff328f
3a66b33
690a971
dc30a49
9c9a9a5
01d4c8f
895d895
556ff21
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,4 +12,4 @@ | |
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
|
|
||
| __version__ = "1.30.0" | ||
| __version__ = "2.0.0-b1" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this a new process, i.e. having a preliminary release instead of immediately switching to 2.0.0? Also, should this be beta or an RC? FWIW, the approach itself does seem sensible to me.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As a semver-major / breaking change, I thought it was reasonable to do a short beta. I could be persuaded that it should be an RC, but I want folks to consider carefully whether they install it in production until we've gotten feedback that all is OK. |
||
Uh oh!
There was an error while loading. Please reload this page.