Hi All,
This coming Monday will be the demo session for train-49, and the
planning session for train-50. Since I won't be able to make it I
wanted to do a bit of async context-setting.
First: please take some time before the meeting to ensure that things in
the "in progress" and "in review" columns have their state accurately
reflected. Experience has shown that the less time we have to spend
working backwards through the waffleboard to get to "next", the better
the meeting will run.
We have two active features that will be closed out with train-49,
meaning we won't need to consider them for train-50:
FxA-27: fennec web login
FxA-29: email quality
Nice work everyone for pushing these through to completion!
We also hoped to close off the service-tokens work, but unfortunately
had to back it out of train-48. Let's double down and try to get it
closed off with train-50:
FxA-31: service tokens
We have three milestones that are just spinning up for new features in
Q4. IIUC the main work for these in train-50 will be finalizing the
initial feature scope and breaking it down into concrete bugs:
FxA-45: device registration
FxA-16: devices view
FxA-38: OpenID Connect
Which leaves a fair bit of headroom below our usual "30 items per train"
workload limit. The vast majority of items in "next" are quality bugs,
so let's take Chris's suggestion to do a quality-focused train.
I've ordered them into roughly what I think is a good priority order,
and I found so many l10n-tooling-related bugs there that I spun up a new
milestone to group them all:
FxA-62: l10n tooling
But the remainder are a pretty strange grab-bag of bugs, so here's a
challenge for us for this cycle:
Each of the 21 "quality" bugs in "next" mattered enough to someone at
some point that they escalated it there. Many are small, and we should
be able to close them out with a focused effort. So let's either get
them done this train, or admit that they're not actually important and
put them back in the backlog, ending train-50 with no "quality" bugs in
"next".
And yes, I realize that means I just volunteered myself for a bunch of
quality-bug work this cycle ;-)
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
