Remove haproxy 1.4#57
Merged
Merged
Conversation
While still not officially unmaintained Willy asked on haproxy's mailing list whether anyone still uses haproxy 1.4 or whether he should set it to unmaintained: https://www.mail-archive.com/haproxy@formilux.org/msg28512.html No one responded that they did. Further reasons for removal: - haproxy 1.4 does not even support TLS - and haproxy 1.5 is only one year younger than Docker itself which makes it unlikely anyone is running haproxy 1.4 inside of Docker.
Member
|
Rock on, this definitely LGTM. That mailing list thread is 😚👌 Thanks! 👍 |
Member
|
(Merging without Travis since it's just a removal, and the part I always forget is included, namely updating |
Contributor
Author
Now it shows the build as failed on the list of PRs, because the PR was merged before the tests even started 😒 😛 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See also my comment on the PR for haproxy 1.7: #35 (comment) 😇
While still not officially unmaintained Willy asked on haproxy's
mailing list whether anyone still uses haproxy 1.4 or whether
he should set it to unmaintained:
https://www.mail-archive.com/haproxy@formilux.org/msg28512.html
No one responded that they did.
Further reasons for removal:
makes it unlikely anyone is running haproxy 1.4 inside of Docker.