-
Notifications
You must be signed in to change notification settings - Fork 29
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
Dependency Upgrade Policy #35
Comments
For upgrade assessments, I think the policy should provide a specific issue template. Generally if we are proposing an upgrade, we have some idea of the motivation. The issue description might start out with empty sections or TBDs, but this can be fleshed out as the upgrade is assessed. It also documents the proposal clearly without having to read through comments. The assessment template could require:
NPM recommends Semantic Versioning1, so it might make sense to fast-track the assessment procedure if no major version bumps are necessary.
As for the review procedure, I think this is pretty much just standard review workflow: open a PR, update dependencies, test with test plan, fix issues and repeat, then merge. I don't think we require any specific information for impl/review per say, but with #34 we may identify things that make sense to document. Docusaurus has provided guidance for a testing workflow2, which is essentially:
Footnotes
|
* Draft Upgrade Policy & Process Fixes #35 * lintfix * upgrade policy updates
Problem
We do not have a policy for upgrading the dependencies we rely upon.
Goal
Our goal is to develop a policy that answers:
Tasks
Define a test planreally just standard review procedure, any strict definition can be done with workflow implSeveral items are out of scope for this issue, but have been acknowledged as potential future work:
The text was updated successfully, but these errors were encountered: