On Thu, Dec 11, 2008 at 11:53 PM, Rakesh Pandit <rakesh.pandit@xxxxxxxxx> wrote: > 2008/12/12 Till Maas <opensource@xxxxxxxxx>: > [..] >>> Right now the report generated is for component: "Package Review" and >>> merge reviews also come under that component. >> >> It seems it was not clear, what I meant. I would like to now, how many of the >> reviews that are done affect Merge Reviews, e.g. add the end of the report >> instead of only this line: >> >> | Total reviews: 40 >> >> It would be nice to have this: >> >> Total Package Reviews: 39 >> Total Merge Reviews: 1 >> >> I would also appreciate a pointer to the script that generates these reports. >> > > I will try to adjust the script to categorize the merge reviews part > of "Package Review" component as separate, probably based on summary > or other attribute of bug. The script is here: > http://cvs.fedora.redhat.com/viewvc//status-report-scripts/?root=fedora > > The one named bugzillaReport.py > > Feel free to patch it up;) > > -- > rakesh I just did a massive rewrite of a large part of the script, I was not sure what new-com and new-incom really did so I omitted them from this version, but I did add in two new reports cvs-com cvs-incom. You will also now get the totals for Merge Review and Review Request. The script also now runs much much faster as it only has to parse around 100 bugs rather then the 8000+ it was doing before. I am linking the script rather then posting a patch as it is so different. If you are interested I would like to add this to our triage scripts fedorahosted project, so we can keep track of features requests easier. If not that is fine too. New script: http://bashton.fedorapeople.org/bugzillaReport2.py --Brennan Ashton -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
