Work Stream | 8/4/2020 | 8/11/2020 | 8/18/2020 | 8/25/2020 | 9/1/2020 | 9/8/2020 | 9/15/2020 | 9/22/2020 |
RM | ||||||||
---|---|---|---|---|---|---|---|---|
Done | 68 | |||||||
In Progress | 18 | |||||||
To Do | 21 | |||||||
Backlog | 5 | |||||||
RA-1 | ||||||||
Done | 42 | |||||||
In Progress | 3 | |||||||
To Do | 10 | |||||||
Backlog | 3 | |||||||
RI-1 | ||||||||
Done | 8 | |||||||
In Progress | 2 | |||||||
To Do | 5 | |||||||
Backlog | 6 | |||||||
RC-1 | ||||||||
Done | 17 | |||||||
In Progress | 1 | |||||||
To Do | 11 | |||||||
Backlog | 7 | |||||||
RA-2 | ||||||||
Done | 26 | |||||||
In Progress | 2 | |||||||
To Do | 33 | |||||||
Backlog | 14 | |||||||
RI-2 | ||||||||
Done | 8 | |||||||
In Progress | 2 | |||||||
To Do | 9 | |||||||
Backlog | 4 | |||||||
RC-2 | ||||||||
Done | 3 | |||||||
In Progress | 6 | |||||||
To Do | 8 | |||||||
Backlog | 2 | |||||||
Edge | ||||||||
Done | 12 | |||||||
In Progress | 0 | |||||||
To Do | 1 | |||||||
Backlog | 0 | |||||||
TSC | ||||||||
Done | 21 | |||||||
In Progress | 0 | |||||||
To Do | 8 | |||||||
Backlog | 5 |
4 Comments
Jim Baker
Hey Scott - I'm not clear on the intention here. We should explore automated ways to collect and report on the developer stats of interest for CNTT. For instance, if all the workstreams had their own repo, LF Insights could report this out easily. I know that would take some re-structuring of CNTT - but it may have some real positive long term benefits. Thoughts?
Jim
Scott Steinbrueck
Hi Jim - sure, I'm very in favor of automation; just haven't explored it yet. For now, I'm just using this as a scratch pad to figure out the data for a week or two. We can talk about options.
Cedric Ollivier
The true question is not about collecting data which is trivial here.
Cedric Ollivier
I don't see any clear reading grid in this wiki page and then I don't understand the outcomes (what's the needs here?).
Interpreting this numbers depends on lot of criteria such as the stream maturity.
It even doesn't help us to understand where we are regarding the planning release (e.g. when RI1 will pass RC1 and then be conformed with RA1).