-
Notifications
You must be signed in to change notification settings - Fork 22
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 0.35.0-pre1 #3359
Comments
I's suggest that we tag the new release once we get the following in the develop branch:
Withoug these, tagging a release would not change nothing as a few of the mentionned commit are already part of the patched version. |
OK! |
This one would need to be part of the release as well:
|
Updated, ready to merge when #3321 is in |
v0.35.0 has been tagged already. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@ashleyvega pointed out that we should tag without the expectation that something is releasable, when the features are sufficiently advanced. It's a good point! Let's do it.
Previous release: #3336
0.35.0-pre1
April 15th, 2021
Improvements
Fixes
The text was updated successfully, but these errors were encountered: