-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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 4.1.0 #4109
Comments
Or version 5, or 4.1. Lets just call it the next release. |
Also, I want this fix #3903 |
Yes, merge some of these pull-requests and pop out a new version. |
Would either @georgepsarakis, @thedrow, or @auvipy be able to address this issue? It's been over 6 months since last release and it appears that there is a decent amount of changes between |
We want to release too. The only maintainer that currently has access rights is @ask and he is unavailable due to personal reasons. |
@thedrow Thanks for the update. Feel free to reach out if I can help move this along in any way. |
Hi everyone, |
nice 👍 |
Glad to hear! You should only have to add release notes for what was merged in after May. |
amazing |
I just got word that amqp 2.2.0 breaks celery somehow. See celery/py-amqp@942b3aa#commitcomment-23064465 |
@gabrielpjordao I released 2.2.1 in response. The breakage is gone. |
Although not very important, I believe naming the version |
i do believe so |
I just released vine 1.1.4 which is a dependency for the next release. |
I just released Billiard 3.5.0.3 as well. I'm going to hold off for a few days with the Kombu and Celery as this is needed to be tested on production . If no one says anything in the next couple of days I'll assume everything is peachy and we'll release Kombu first and then Celery itself. |
In case someone wants to contribute #3934 requires test coverage in order to be merged and we'd like that to hit 4.1 as well. |
@georgepsarakis made celery/kombu#770 to discuss failure. Trying to get it resolved but could definitely use some input if anyone's feeling keen. |
@alukach please check the Pull Request in sphinx-celery. If you could try and verify that my branch solves the issue, it would be great. |
Kombu 4.1.0 was released! 🎉 |
@thedrow Great work! Can we merge celery/sphinx_celery/pull/2 ASAP? It feels like issuing a release with a failing build is bad mojo. |
@thedrow Thanks for the merge, now if either you or @georgepsarakis could trigger a retry on https://travis-ci.org/celery/kombu/jobs/255735887, we should have a passing build! |
@alukach this won't affect the build job you are mentioning, because the |
@thedrow requirements files for both Kombu and Celery use |
@georgepsarakis Unfortunately I don't have access to that package. @ask forgot to add me to that one. |
As of now we're in merge-freeze zone. Unless something very critical pops up on Monday, we'll release Celery 4.1.0. The only thing that is left is the release notes for Celery. Any volunteers? |
@thedrow since we are using requirements files we could use the Github repository directly, if you don't get access any time soon. I am also adding a comment by @alukach, regarding an easy way to summarize changes, for reference: celery/kombu#764 (comment) |
I just released 4.1.0. |
I am not aware of how celeryproject is deployed. @auvipy could you please do it? |
Also, documentation does not seem up-to-date: http://docs.celeryproject.org/en/latest/index.html still shows 4.0.2 . Is there something we can do to update it? |
yes I can do the announcement blog. |
it's indicating 4.1 http://docs.celeryproject.org/en/master/index.html |
Also, pretty minor, but the README (and hence pypi description page) state that:
Version should be bumped to 4.1, and Python list extended with Python 3.6 |
@auvipy yes, this is for the master branch, see the latest though: http://docs.celeryproject.org/en/latest/index.html |
I'm done with the blog post, just need the whats new changlog |
Echoing what @georgepsarakis has reported, |
Note, the above issue also exists with the Kombu docs |
Looks like @thedrow appears to have owner access to fix that. Admin -> Advanced Setting -> Default branch. |
Great work on the release! 🎉 RTD points to the 4.0 branch, simply because that's supposed to be the branch Since this is a 4.1 release, that has usually meant creating a new branch for that, but if minor releases are frequent it's reasonable to keep using the 4.0 branch). |
Ah, I see. I think there is also the option to set the default version to |
The automated release process doesn't bump the docs configuration. |
subj
The text was updated successfully, but these errors were encountered: