Developer Issue Tracking
Background: We have a lot of ways that developers can submit issues and pain points in our repos, this forum, our slack, the weekly meeting etc. We want to do a better job integrating this information, so that we know what to prioritize and when. And finally, we’re trying to address 3 issues per cycle, so we want to have a public place to announce those.
Desired Outcome: I want to make sure that we have a good plan for logging issues as they come in, but more importantly, I think we should decide on a venue for public information about which issues we are working on in a given sprint cycle (we’re going to try to address 3 per cycle).
- Different functional groups will do proposed issues for each
- Post issues to the public engineering meeting thread
- Community changelog (automated change log generator?)
Outcome: Aaron will make a plan.
You can also just add an automated changelog generator to each repo and put them in place. For collecting changes.
Test coverage vs shipping fast
Background: Do we want to consistently enforce test coverage requirements on pull requests?