Skip to content
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

Make sure PServeCommand kwargs are passed to the hupper worker. #2974

Merged
merged 2 commits into from
Mar 6, 2017

Conversation

mmerickel
Copy link
Member

Backport of #2962 to 1.8-branch.

@mmerickel mmerickel force-pushed the backport-2962-to-1.8-branch branch from f3d4fff to 108a23f Compare March 6, 2017 00:43
mmerickel added a commit to mmerickel/pyramid that referenced this pull request Mar 6, 2017
@mmerickel mmerickel force-pushed the backport-2962-to-1.8-branch branch from 108a23f to 6eceb02 Compare March 6, 2017 00:44
@mmerickel mmerickel merged commit fcb470c into Pylons:1.8-branch Mar 6, 2017
@Natim
Copy link

Natim commented Mar 9, 2017

Hi @mmerickel Would you have some bandwith to cut a 1.8.3 release with this fix please?

@digitalresistor
Copy link
Member

@Natim Are there any other issues that need fixing first? Cutting releases takes a bit of time and we don't want to have to spin 1.8.4 tomorrow...

@Natim
Copy link

Natim commented Mar 9, 2017

If they were I would have filed PR...

@mmerickel
Copy link
Member Author

If they were I would have filed PR...

We were just referring to the last release when you opened a new bug report a day after, so it would be appreciated if you tested the unreleased 1.8-branch first to avoid anything obvious showing up immediately again. Plus you will get them fixed sooner without waiting a few weeks for another release.

Regardless, please don't take that as an insult, I certainly appreciate the bug reports. I will cut a release this weekend at the latest with the changes.

@Natim
Copy link

Natim commented Mar 9, 2017

As far as I know we didn't detect any bug since this one. I will test the branch tomorrow. I am a bit worried that you feel it is hard to do a release, maybe we should change the process to make it easy.

In our team we are using zest.releaser and updating the changelog in each PR so it is really easy to cut a release.

@stevepiercy
Copy link
Member

@Natim releasing is not hard, it is merely time consuming. See our complete checklist, RELEASING.txt.

If zest.releaser can automate all or most of all those details, I'd like to know more, but let's discuss in a new separate issue as a feature request.

@Natim
Copy link

Natim commented Mar 10, 2017

Apparently we actually did :( #2975

@mmerickel
Copy link
Member Author

@Natim that's a change of a default... that won't be going into a 1.8 bugfix release unfortunately.

@Natim
Copy link

Natim commented Mar 13, 2017

Ok then we are good for 1.8.3

@mmerickel mmerickel deleted the backport-2962-to-1.8-branch branch November 29, 2020 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants