Hi, On 12 May 2011 08:40, Ilias Biris <[email protected]> wrote: > Hi > > related to monitoring, while looking at the status.linaro.org, I thought > of the following:
There's a spec for status v2. The idea is to finish status v1 and improve it. See https://wiki.linaro.org/Platform/Infrastructure/Specs/LinaroStatusV2 > - any impediments to TRs should be shown clearly, I have the feeling > that I would need to dig into individual items in order to find out > impediments > > - list of changes (change in blueprint priorities, deferral to next > cycles) should be shown > > - is it possible that the header for each WG section could take to that > group's overall status - perhaps with a burndown chart for the group as > well as estimation on how many work items per day are needed to meet the > target for that group? > > - related to the rate of WI's per day needed in order to complete the > work is it possible to show also the actual completion rate per day? > > - are there any other metrics we should be having? Eg bugs counts > (inflow,outflow of bugs, bugs waiting for release etc), and bug trends? > Right now I would need to dig into individual blueprints to find out the > bugs situation - or is there some other place I can get a highlight if > needed for the bugs associated with the blueprints of a working group? We need metrics definitely. I started to discuss it with James W. See https://wiki.linaro.org/Platform/Infrastructure/Specs/BugMetrics > - finally, since we are going into monthly releases (George actually > mentioned even daily releases in his opening speech) then I would like > to see the status also on a release base. Is that in the pipeline to be > supported? Cheers, Fathi _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
