On 22/12/2015 20:41, Douglas Turner wrote:
My suggest was to take the n-th milestone was a strawman. I think in terms of scheduling, setting aside every n-th milestone as a quality release helps planning a bunch. When we tell customers (the web, the firefox team, firefoxos) that feature X will be delivered by Aug, we can build in time to sharpen our axe.
On Hello, we've being attempting to take care of quality slightly different. We're working in an agile manner, and for each cycle, we're trying to allocate a certain amount of time to fixing bugs, addressing technical debt, and other quality issues. I can't remember the exact percentages at the moment, but I know we originally discussed something like 20%. The remaining 80% is spent on feature work. We're also starting to expect/allocate more time for fully implementing features after the "initial" implementation is complete.
We've only been trying this over the last couple of months, and with other changes going on at the same time, I think its too early to say how successful we're being. For me, the positive part, is that we're constantly thinking about quality and improving the code base, rather than doing it in spurts when it gets very bad.
Mark. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
