Avoiding regressions¶
Status: Draft Review status: Draft Theme: code quality, user experience, developer experience
Team¶
Project owner: ???
Role | Assignee | Reviewer | Notes |
---|---|---|---|
Requirements | Kriti | Ghislaine, Dom, Rajat | Product spec, requirements, GitHub issues |
Design work | Ghislaine | Kriti, Dom, Rajat | UI and UX |
Backend work | Dom | Mukesh | Backend specs and code |
Frontend work | Rajat | Pavish | Frontend specs and code |
Problem¶
We noticed a number of regressions through manual testing for the release of 0.1.3. We need a more robust solution.
Solution¶
This is still under discussion. See the developer group conversation.
Outcome¶
We need to determine: - If we want to tackle this now. - How we want to tackle it (see the thread for discussion) - Tackle it (if first two bullet points are handled)
Risks¶
TODO
Links¶
Information
This section collects project related links. It’s expected that there might not be anything here until the project plan is approved, and this section will grow over the project’s timeframe.
-
Issues: GitHub meta issue
- Wiki pages:
- Product spec
- Backend spec
- Frontend spec
- Email discussions:
- Weekly updates
Timeline¶
TODO