With commit 623587c76d a script to expire
old bug reports got introduced. This change updates a few things:
* print an ascii table after the bug reports has been closed
(in case you want to paste it on the ML)
* fix the script argument "--no_dry_run" to fit the conventions
* Change the bug task status from "won't fix" to "expired" (this
feedback came from the ops ML [1])
* improve the wording of the bug comment a little
* avoid the INFO logging of used libs
[1] http://lists.openstack.org/pipermail/openstack-operators/2016-May/010577.html
Change-Id: I6055ba4bfc8d08998a0e8451fe515a2b4796ce72
With commit 623587c76d a script to expire
old bug reports got introduced. This change updates the docs in the
"README.rst" to reflect that.
It also makes the script executable (chown +x) so that it is
consistent with the other scripts and in this folder.
Change-Id: If6e1d7f79731549e30feeddada0a561d609d56dd
Many OpenStack projects face the issue to have more bug reports than
they can handle with the resources they got. The chances, that the
same setting which leads to the observed issue is still there, is quite
often unlikely. It's better to be explicit and expire old bug reports
which will not get any attention any more.
Change-Id: I3c9c72b528b090647211262d2f0030d66be9857c
Jeremy Stanley