-
Notifications
You must be signed in to change notification settings - Fork 271
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
Prepare 6.2.0 release #1256
base: master
Are you sure you want to change the base?
Prepare 6.2.0 release #1256
Conversation
CHANGELOG.md
Outdated
@@ -4,8 +4,10 @@ This document describes changes between each past release. | |||
|
|||
## 6.1.2 (unreleased) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving from setup.cfg
to pyproject.toml
should probably be considered a breaking change. I agree with a previous comment of yours (where you told it would be better to not do things in this order and issue the quick fix first), but it's also probably too late now.
To me, it's at least a new feature (so updating the minor, to 6.2.0), but probably a breaking change, so we should update the major (7.0.0)
I agree we are in an annoying situation, with both a "bugfix" and a "feature" release in sight. I suggest an alternative route:
@almet what do you think of this plan? If you agree, I can do the backport release this week-end or next week. |
Maybe this worth waiting on #1258 as this is also a big change? I will try to move this forward in the weekend
Sounds reasonable to me. |
That sounds like a plan :-)
|
Great :) I've just released 6.1.2 and backported changelog and CI changes in #1266 I'll update this merge request accordingly. |
I would like to release 6.1.2, mostly because of the fix for
generate_password_hash
.I will add an entry about #1244 once it's fixed.
According to our new repository rules it needs another maintainer approval or a delay of one week.