Conversation
It has been a few years since the last update and jemalloc has had several releases in that time. I've been maintaining my fork and provided support on it for a couple years now and I think it's time to deprecate this one. This buildpack has had a great life (and should continue to work as is) but I think it's worth it to steer folks toward a maintained fork. For example, it was recommended for Ruby to skip the 4.x branch and to stick to 3.6.0 (released in 2015), but our team has had really good luck with 5.1.0 and 5.2.0. There was a [pull request](#18) to merge the fork into the buildpack but given the risk it would expose anyone using the current buildpack to I don't think it is a good path forward. For more details see this comment: #18 (comment)
Collaborator
|
Cheers! Maintained is better than not! I agree that leaving this as a "historical artifact" for current users that don't want to upgrade is preferable to merging. |
Owner
|
👍 to that! |
Collaborator
Author
|
🎉 Thanks guys |
Owner
|
Thank you for continuing to maintain a jemalloc buildpack!! |
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
3 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.
It has been a few years since the last update and jemalloc has had
several releases in that time. I've been maintaining my fork and
provided support on it for a couple years now and I think it's time to
deprecate this one.
This buildpack has had a great life (and should continue to work as is)
but I think it's worth it to steer folks toward a maintained fork. For
example, it was recommended for Ruby to skip the 4.x branch and to stick
to 3.6.0 (released in 2015), but our team has had really good luck with
5.1.0 and 5.2.0.
There was a pull request to merge the fork into the buildpack
but given the risk it would expose anyone using the current
buildpack to I don't think it is a good path forward. For more
details see this comment: #18 (comment)
@mojodna @nateberkopec thoughts?