Marketplace/Keeping The Lights On
Just like keeping the moss off the roof of your house or changing the oil in your car, owning software means regular maintenance. Often this comes in the form of upgrading libraries and dependencies as newer versions are released - at a minimum this means security fixes, but could also include other enhancements like performance improvements or new features.
With software which is still actively developed there are additional obligations. Adding new features means they need to work with the existing feature set. This may work out with small changes but over time debt is built as we move further away from the original design of the software. After a certain amount of debt accumulates we can reduce it by considering how the software has evolved and redesigning portions of it.
In addition to feature-driven debt there are small "papercuts" which appear after software has been used for a while and the kinks are worked out. These papercuts are important to fix, not only because they add to the debt burden but they are often legitimate concerns experienced by our users (hopefully not as a first impression).
Finally, there is a portion of maintenance which is more forward thinking and includes scalability planning for the future, security analysis and response, and analytics adjustments as questions about site performance come up and we need to answer them.
In the Marketplace, we're calling this maintenance work Keeping The Lights On (KTLO) and we make progress on it in focused chunks called Chapters. They are below.
Tracking bug: 1205830
|1102883||Recommendations checkbox does not work correctly||P2||RESOLVED|
|1188073||[tracker] KTLO Chapter Two||--||RESOLVED|
2 Total; 0 Open (0%); 2 Resolved (100%); 0 Verified (0%);
Tracking bug: 1188073
|1175691||[tracking] Investigate db inconsistencies between docker/dev and stage/prod.||P1||RESOLVED|
1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%);
This chapter focuses on the first thing our new users see: the consumer pages component.
Tracking bug: 1135257 RESOLVED FIXED July 27th, 2015 About 1/3rd of the bugs closed in this cycle were from 2014 or before. Priorities leaned higher than we expected closing five p2 bugs, four p3 bugs, two p4 bugs, and four p5 bugs. One bug was closed by a contributor, Atique.
15 Total; 0 Open (0%); 7 Resolved (46.67%); 8 Verified (53.33%);