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
We need to review the tech debt left over from the CWM project and before.
Resolution
This issue is to collect and itemise the known tech debt. As such there's no hard deliverable, this is more of a collection point for linking to and spinning out new issues. This can be kept around until it's not considered useful.
The text was updated successfully, but these errors were encountered:
How do we manage the current co-existance of MM 4.x and 3.x deployments, and ideally resolve into a lower-maintenance situation? (Presumably by replacing uses of the latter with the former.)
What obstacles exist to that?
Cross-skilling of devs needed. Which portions which are a one-developer silo?
Unit / regression tests. What exists, and what is missing?
Documentation. What exists and what is missing? Which is most problematic?
Hacks and workarounds. What exists and which are most risky?
Missing features. What exists and which are most problematic?
Servers and infrastructure and tools. What is in use? What is neglected? What is precarious in the face of staff changes, server crashes, or unexpected demand?
Problem
We need to review the tech debt left over from the CWM project and before.
Resolution
This issue is to collect and itemise the known tech debt. As such there's no hard deliverable, this is more of a collection point for linking to and spinning out new issues. This can be kept around until it's not considered useful.
The text was updated successfully, but these errors were encountered: