On 13/06/2015 02:09, Christopher Karlof wrote: > Hi all, > > I wanted to share with you how the Firebug team reports weekly status.
That's cool and very detailed. Do you suppose this would be (or could be) mostly-automatically-generated from bug activity? Would folks on this list be interested in seeing a similar weekly report for FxA, perhaps broken down by major components to keep it manageable? Ryan > ---------- Forwarded message ---------- > From: *Jan Odvarko* <[email protected] <mailto:[email protected]>> > Date: Fri, Jun 12, 2015 at 8:16 AM > Subject: Firebug Status > To: [email protected] <mailto:[email protected]>, > [email protected] <mailto:[email protected]> > > > == May 8-14.6 2015 == > > === Monday === > * WIP Bug 1168872 - Support for server side logging > * REVIEW (patch for RDPi provided by Luca) > ** Feature: enable/disable packet cache #40 > ** Each child in an array or iterator should have a unique "key" prop #41 > > === Tuesday === > * Firebug 2 > ** REVIEW #7907 monitor() and debug() commands don't place breakpoints > correctly #7908 > ** Patch provided by Florent > * WIP Bug 1168872 - Support for server side logging > * REPORTED Bug 1172887 - Move getfirebug.com <http://getfirebug.com> to > different location > * MEETING Extending Devtools weekly meeting > ** Notes: https://etherpad.mozilla.org/extending-devtools > > === Wednesday === > * WIP Bug 1168872 - Support for server side logging > ** Testing on B2G > > === Thursday === > * WIP Bug 1168872 - Support for server side logging > ** Testing on B2G > ** Automated test created > > === Friday === > * WIP Bug 1167080 - Trigger HAR export from within the content > * ANALYSES Bug 1171927 - Fine tuned logging in devtools code > > Honza > > > > > _______________________________________________ > Sync-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/sync-dev > _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
