By the way, I just looked at the total (i.e. for all projects) number of issues unresolved as compared to the total number of issues assigned to the release. The ratio is 341 / 722, or abouit 47%. This means that less than one month from the release, we've resolved less than half the issues assigned to the release, and that doesn't even take into account the large number of issues that are unassigned to a release.
My takeaway from this is that we either are way behind in completing tasks for the release, or we need to improve our JIRA bookkeeping, or some combination of all of the above. David On Fri, Aug 26, 2016 at 4:59 PM, David McBride <dmcbr...@linuxfoundation.org > wrote: > Team, > > Some updates for this week's report: > > 1. My script will how automatically add any missing versions to your > project, so you no longer need to worry about that task. To be clear, the > script simply makes the version strings available for selection in your > project. It does not assign any issues to those versions. > 2. The script also now determines the ratio of unresolved issues to > total issues assigned to the current release (i.e. Colorado 1.0) > > Observations: > > - The percentage of projects with no unassigned issues improved > slightly from 15% to 25% since my first report. > - However, this still means that 3/4 of OPNFV projects still have > unassigned issues. We cannot do meaningful analysis of progress without > knowing which version issues are assigned. > - Note that all projects now have the "Future Release" version > string. So, if you do not plan to resolve an issue for the current > release, and you aren't sure that you will do it in the next release, > then > assign it to "Future Release". > - We are less than one month out from the Colorado 1.0 release, yet > there are a startling large number of issues assigned to the release that > are unresolved. > - Please make sure that you are updating the status of your JIRA > issues whenever there is a relevant change. Don't let fixed issues > remain > reported as unresolved in JIRA. This creates a lot of ambiguity when > trying to understand the status of the project. > - For issues assigned to Colorado 1.0 that you don't believe will > be resolved by the release date, you should start reassigning those to > Colorado 2.0, or some other future release. Our goal is to have zero > issues assigned to Colorado 1.0 by the date of the release. Don't wait > until the last minute to move the issues. > - Alternatively, if you believe that an issue is no longer relevant > or important, then simply close it. If you're wrong and the issue is > important enough, then it will resurface. In the mean time, there's no > use > in suffering the overhead. > > Let me know if you have any comments or questions. > > -- > *David McBride* > Release Manager, OPNFV > Mobile: +1.805.276.8018 > Email/Google Talk: dmcbr...@linuxfoundation.org > Skype: davidjmcbride1 > IRC: dmcbride > -- *David McBride* Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: dmcbr...@linuxfoundation.org Skype: davidjmcbride1 IRC: dmcbride
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
