Markus Zoeller/Germany/IBM@IBMDE wrote on 03/10/2016 11:06:24 AM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List" <[email protected]> > Date: 03/10/2016 11:07 AM > Subject: [openstack-dev] [nova] bug status "incomplete" is *not* a closed state. > > Just a short reminder that the bug status "incomplete" is *not* a > closed state. It is an open state like "new" and "confirmend". > Setting "incomplete" means that we need more information to assess > this bug report and it should be explained in a comment *what* is > missing. Without this, a reassessment gets unneccessary hard [1]. > Closed states are: "Invalid", "Opinion", "Won't Fix" and "Fix Released". > > References: > [1] > https://wiki.openstack.org/wiki/ > BugTriage#Task_4:_Review_incomplete_bugs_.28anyone.29 > > Regards, Markus Zoeller (markus_z)
For the sake of completeness: If you set "incomplete" because you rely on the auto-expiration from the Launchpad janitor, please keep in mind that the auto-expiration [1] of a bug report only happens if: * it has not been assigned to anyone * it has the "Incomplete" status * the last update was more than 60 days ago * it is not marked as a duplicate of another bug * it is not targeted to a milestone. Right now we have 22 bug reports which are "incomplete" but don't auto- expire because one of the other conditions is not met. Additional effort by the bugs-team is necessary for that cleanup. References: [1] https://help.launchpad.net/Bugs/Expiry Regards, Markus Zoeller (markus_z) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
