Skip to content

Remove 3.7 #431

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

Merged
merged 1 commit into from
Aug 18, 2020
Merged

Remove 3.7 #431

merged 1 commit into from
Aug 18, 2020

Conversation

tianon
Copy link
Member

@tianon tianon commented Aug 14, 2020

3.7 goes out of any kind of support on October 1st. There will be one more security patch release of 3.7.x, after that, we can basically assume the 3.7 flavour of this image won't have any upstream releases to benefit from.

Honestly, the attack 3.7.28 will address is local, requires elevated privileges and is Windows-specific. So this image isn't really affected.

@michaelklishin
Copy link
Collaborator

@tianon if we wait for 3.7.28 to be produced and published, we'd have likely the last 3.7 release up on Docker Hub. Then we can merge this.

@michaelklishin
Copy link
Collaborator

A version with 3.7.28 has been published. Should we merge this @tianon @gerhard?

@tianon
Copy link
Member Author

tianon commented Aug 17, 2020

Once we get docker-library/official-images#8568 merged, I'll rebase and merge 👍

@tianon
Copy link
Member Author

tianon commented Aug 17, 2020

(Unless @gerhard objects to removing 3.7 before then -- we can always bring it back again if we need to)

@gerhard
Copy link
Contributor

gerhard commented Aug 18, 2020

No objections @tianon.

RabbitMQ release series 3.7 reached end of General Support on 31 March 2020, which is what open source users care about, including the overwhelming majority that uses this Docker image.

With 3.7.28 out & merged, it's a good time to stop supporting 3.7 in this Docker image.

> 3.7 goes out of any kind of support on October 1st. There will be one more security patch release of 3.7.x, after that, we can basically assume the 3.7 flavour of this image won't have any upstream releases to benefit from.

> Honestly, the attack 3.7.28 will address is local, requires elevated privileges and is Windows-specific. So this image isn't really affected.

- Michael Klishin
@tianon
Copy link
Member Author

tianon commented Aug 18, 2020

Ok, rebased, green, all is well. Let's do this. 😄

@tianon tianon merged commit 99dc809 into docker-library:master Aug 18, 2020
@tianon tianon deleted the bye-3.7 branch August 18, 2020 17:24
docker-library-bot added a commit to docker-library-bot/official-images that referenced this pull request Aug 18, 2020
Changes:

- docker-library/rabbitmq@99dc809: Merge pull request docker-library/rabbitmq#431 from infosiftr/bye-3.7
- docker-library/rabbitmq@13daa51: Remove 3.7
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.

3 participants