-
Notifications
You must be signed in to change notification settings - Fork 572
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
Release v0.8 #899
Comments
If you think the monthly pace is suiting this library ATM, I'm fine with it. Otherwise I'd be fine slowing down the release cycle as well. |
I think the monthly pace suits this library quite well: we want big features like the ability to open PRs/discussions rather rapidly; as it won't make it in this release, I think it would be a bit painful to wait two months after v0.8.0 in order to have that feature in a release. Having a monthly pace solves that problem with no downsides :) |
Two PRs ought to be in this release as well:
|
I think we can close this :) |
Starting in April we started implementing a monthly release schedule: v0.5.0 in early April, v0.6.0 in early May. v0.7.0 was released shortly after as a commit was lacking from v0.6.0 and was needed for the
evaluate
release.I am proposing to release v0.8.0 next week, which would act as the successor to v0.6.0. The v0.8.0 milestone contains three PRs which need to be merged:
metadata_update
: work on a copy of the upstream file, to not mess up the cache #891Additionally, there are a few deprecation warnings that should now error out. This includes the
login
command as describe in #827, cc @PierrciThe text was updated successfully, but these errors were encountered: