-
Notifications
You must be signed in to change notification settings - Fork 822
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 2.40.0 #2174
Comments
Two reasons I haven't done any release yet:
I will pick up the next release soon. |
At least bookshop and library will look different now, so new release would make the difference. |
I also considered pushing release, but I decided to wait until #2101 is resolved. |
I have reverted #2101 for now as it is blocking the release. |
With that reverted, are you ready to tag a release? |
Done, see also openstreetmap/chef#70. |
Thanks! |
A month ago I ran out of time to make a release before I left on a holiday. I've realised that I'm a single point of failure with releases, and despite telling all the other maintainers that the are welcome to take over, I think everyone is still waiting on me to do them!
So I'm going to make a new policy, which is that I want to see every maintainer making a release at least once a year, just to make sure that everyone is comfortable doing so if I'm not around. I'm happy to continue as the main release manager, and I'm also happy to hand over to others. But I think it's worth making sure all the maintainers are happy with the release process.
I've assigned this issue to @math1985 to make the next release, which can be done any time from now.
The text was updated successfully, but these errors were encountered: