Nice work! We had something similar (kind of outdated) tracking 1.2, 1.3 and 1.4 (versions are customisable so it should be easy to change).
Based on some comments from Dietrich I tried to create something that worked offline and minimised the amount of Bugzilla requests so I ended-up using Firebase to keep track of app data and using appcache. Thanks to that, the tracker should be able to work offline and use the latest data you downloaded from Firebase. It can be installed as Firefox App (Desktop and Mobile), Chrome App or you can add to home screen in Chrome for Android or iPhone/iPad. The tracker is here: http://dcoloma.github.io/ffostracker/home.html The code is also on github: https://github.com/dcoloma/ffostracker The Firebase instance I have is already tracking components, nominations and so on, so I think it should be easy to add the missing features you have included about components etcŠ It is available at: https://owd.firebaseio.com/ Cheers! El 10/03/14 00:50, "Andreas Gal" <[email protected]> escribió: > >I made a little dashboard for the B2G release status. I expect this to be >eventually replaced by a more powerful dashboard Dietrich is working on. > >http://andreasgal.github.io/dashboard/ > >All the data in the dashboard is pulled live from Bugzilla. >Hidden/confidential bugs are not included in the counts (those numbers >tend to be tiny, I can see every bug in the system and its off by less >than 5%). > >Nominations are all the current nominations for active releases. Release >management should work on keeping these close to 0 at all times. We >definitely have way too high numbers here at the moment. > >Triage lists all the bugs in the ³General² component. I have asked QA and >release management to make sure this bucket is also near 0 at all times. >Nobody feels responsible for bugs in this category. > >Sometimes we have non-code bugs in the ³General² component. We should >either make sure those are all tagged as NPOTB so we can exclude them in >the counter, or maybe we should simply not bock on them with the >b2g-blocking flag. > >The blockers area lists the blockers for each release for each component. >You can click on the counters to see the list directly in Bugzilla. The >goal is for each team to keep the list of their blockers near 0, and only >do feature work if we are confident that the blocker list will not cause >problems for the release schedule. > >We currently don¹t have a 100% match of team structure and components in >Bugzilla. Some teams own more than one component (thats ok). Some >components are owned by multiple teams (thats less ok). If you know of a >case where our current component structure doesn¹t fit well the team >structure, please email me directly and we should discuss changing one or >the other. > >The source for the dashboard is up on github. Please send a pull request >if you have an idea how to make it better. > >Thanks, > >Andreas > >PS: The dashboard has a couple power user features: > >http://andreasgal.github.io/dashboard/?releases=1.3,1.3T&reload=60 > >This only shows the 1.3 and 1.3T releases and reloads the dashboard data >automatically every 60 seconds. >_______________________________________________ >dev-b2g mailing list >[email protected] >https://lists.mozilla.org/listinfo/dev-b2g ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
