-
Notifications
You must be signed in to change notification settings - Fork 776
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
Update the "Application dependency management" recommendations #1055
Update the "Application dependency management" recommendations #1055
Conversation
234e093
to
d83a050
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. I took the liberty of pushing some copy edits, and I have one content question.
87bd7e2
to
79238e3
Compare
This is a more detailed recommendation that breaks up the recommendation into multiple parts, to reflect that multiple tools need to be used in workflows today to maximise compatibility with existing platforms. It also recommends that deployed applications be isolated from the system packages, as was implied but not explicitly noted. The move away from Pipenv as the primary recommendation is a reflection of the change that application development workflows have a greater diversity in mature tooling available for them. Co-authored-by: Brian Rutledge <bhrutledge@gmail.com>
79238e3
to
8c8550d
Compare
@bhrutledge I've rebased this on |
This is a more detailed recommendation that breaks up the recommendation
into multiple parts, to reflect that multiple tools need to be used in
workflows today to maximise compatibility with existing platforms.
It also recommends that deployed applications be isolated from the
system packages, as was implied but not explicitly noted.
The move away from Pipenv as the primary recommendation is a reflection
of the change that application development workflows have a greater
diversity in mature tooling available for them.
Toward #912