Thu, Dec 13
Tue, Dec 11
Tue, Nov 27
The post mortem process now includes a section on test/escape analysis.
Current unit test coverage has become part of the Code Health newsletter. Code coverage numbers will also be a key component of what is reported through the Code Health Metrics.
Progress to date:
- Slow going at first as this is a shared goal. Originally a Q1 goal, this has moved to a Q2 goal in order to allow CPT to get through some of its PEP planning.
- Meeting with CPT this week to plan next steps.
Progress to date:
@Catrope, we can certainly find another home for this extension if you think another team is a better fit. Out of curiosity, is this related at all to the change from Collaboration to Growth? I'm trying to get a sense of whether the wrong call was made when we first reviewed this extension for Code Stewardship or if things just changed since then.
Nov 15 2018
Nov 6 2018
@Aklapper, I was thinking that simply removing it from Developers/Maintainers would suffice from a documentation perspective. As maintenance of Developers/Maintainers page is currently manual and this removal comes as a result of the code stewardship review process, I'll make the edit(if it's not already been removed).
@Liuxinyu970226, yes that makes sense.
Nice work all!
Oct 29 2018
Oct 25 2018
Oct 22 2018
Oct 12 2018
Oct 3 2018
Forgot my password :-( Waiting for reset.
Yeah, not a stellar job of documentation :-) I'll do a better job next time. I do want to followup to make sure that this made it through the change from Collaboration to Growth.
@Krinkle, it's supposed to mean that a Code Steward has been found/assigned. In this case it was the Collaboration team. Which is now the Growth team if I understand correctly.
Oct 2 2018
Sep 25 2018
Sep 24 2018
Makes sense to me.
Sep 21 2018
Sep 13 2018
@Aklapper you are amazing! I even commented on that task and don't remember it :-) It is a dup. I'll move stuff around shortly (have parent and child tasks to take into consideration).
Sep 6 2018
@Aklapper, I've been spending a bit of time on this and one of the directions I'm leaning is to have the ROO be an output of the deployment review process (Review Queue today). My thought being that the ROO could be used by deployers as an authoritative source to determine whether or not a new extensions, services, etc... should be deployed. I spoke a to Tyler a bit about this and it seems like it would be of value.
After some initial thought and discussions regarding this goal, it seems that a closely coupled area of concerned is that of the Review Queue (the process by which extensions are reviewed prior to initial deployment).