You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we have a policy for integrating package dependencies?
My view on this is that we should include these carefully and only as absolutely necessary.
For example, we could agree to the following:
Only consider dependencies which are stable, supported and frequently updated.
Always justify the addition of a dependency based on user requirements.
Always discuss the potential introduction of a dependency before merging with the main branch. Ideally, bring it up for discussion even before testing.
Use environment stack. Should keep development packages (e.g. profiler) separate from deployment ones.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Should we have a policy for integrating package dependencies?
My view on this is that we should include these carefully and only as absolutely necessary.
For example, we could agree to the following:
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions