Can we cut a new release?
We've seen large performance improvements with https://github.com/benoitc/gunicorn/commit/f145e90e322256f1c4e1eea8e175d2e188ceab43 and would love to be able to use it without forking 馃槃. If master isn't ready to go out can we publish a hotfix with that commit on top of 20.0.4?
馃憤 for this and it鈥檚 backport
Looks like it's already backported.
I invite everyone to take a look through recent changes on master and propose additional backports in this thread. Please also flag anything breaking, otherwise we can release as 20.0.5.
Help preparing the changelog / news most welcome, too!
i can take care about the release tomorrow. please yes flag any breaking change.
I propose this release be Gunicorn 20.5.0, unless someone sees breaking changes.
I also to propose to include #1450, since it is a backwards compatible change.
Ack, I said "20.5.0" but that's because I thought we were at "20.4.0". Instead, we have done four patch releases of "20.0.x".
I think I propose "20.1.0" then. Does that seem right?
@tilgovi why ? Is there any change outside a patch?
There are some new features, but small:
--print-config
CLI flagwsgi_app
config valueNone of these are major. I don't worry about breaking anything, but I default to calling it a minor release because there are these new features.
i agree, it should be a minor release :)
@tilgovi @benoitc anything I can do to help this release get out?
i have been side tracked. I will take care about a release on thursday
@rowillia any test on current master is welcome :) Thanks!
@benoitc if there's anything I can do to help prepare, let me know. I'm happy to update NEWS or anything like that.
Ditto
Will this release include #2304 and #2313? First time user of gunicorn and in here. I am happy to help what I can!
Yes, @tibudiyanto. The new version will include everything on master.
@jamadden @tilgovi sorry i have been side tracked. I will come back to you asap. Lest plan a release on next Tuesday .
Been running https://github.com/benoitc/gunicorn/commit/4bed9e7b192ae211b7d1f6c14065c373c9e1c0aa in production for about 24 hours so far and everything is looking good. The keepalive shutdown fixes really helped with 503
s we were getting when deploying or hitting max_requests
and waiting for the worker to exit. Looking forward to the release.
Friendly ping - anything I can do to help this get out? We've been running these patches for a while and it's been great for us.
superseded by #2370. I take about it today.
Most helpful comment
@jamadden @tilgovi sorry i have been side tracked. I will come back to you asap. Lest plan a release on next Tuesday .