-
Notifications
You must be signed in to change notification settings - Fork 136
Automation improvements #2123
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
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
[Triage] It would be beneficial to identify which issues would still exist with ArPow. Additionally we would like to identify phases w/the idea being the top phase would be the items we would like to tackle first. Once the phases are identified, they should be reviewed by the triage team. |
Based on value/effort ratio, "shovel-readiness", and usefulness after ArPow I recommend these for the first pass:
And these for later implementation:
And the rest for later re-evaluation. |
[Triage] The decision is that we will commit to fixing one issue per servicing cycle. @crummel, please add to project board and assign milestones. |
[Triage] This is superseded by #3065 |
Situation
There are currently many manual steps in and around our build and release process for servicing. These cause problems because they can be easily forgotten, they may not be done consistently between servicing events, and they make servicing take longer.
Objective
Improve servicing ease and turn-around times by automating work that is currently done manually. Prioritize work that is easier to automate and takes the most effort manually.
Execution
Identify opportunities for automating manual servicing work, estimate and prioritize them. All these improvements should be small and independent so improvements can be made gradually whenever we have time. Ideally we will make at least one improvement per servicing cycle that we can then try out in that cycle.
The text was updated successfully, but these errors were encountered: