Last modified: 2014-09-25 20:24:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61831, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59831 - Bugs with abandoned changes shouldn't be PATCH_TO_REVIEW
Bugs with abandoned changes shouldn't be PATCH_TO_REVIEW
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
wmf-deployment
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-08 20:06 UTC by Jackmcbarn
Modified: 2014-09-25 20:24 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jackmcbarn 2014-01-08 20:06:59 UTC
When a Gerrit change for a bug is abandoned, if the bug is PATCH_TO_REVIEW, Gerrit Notification Bot should change it back to its previous status when it posts the abandonment message.
Comment 1 Andre Klapper 2014-01-09 14:06:38 UTC
Just adding a comment that I don't have a strong opinion on this.

Jack's point is valid (especially when it comes to the wording TO_REVIEW), but patches might be abandoned also for non-technical reasons (e.g. submitter not interested anymore, or bug 39139 comment 8), and might still make a bug "closer" to getting fixed when somebody picks up the (abandoned) code again.
Comment 2 Makyen 2014-09-25 18:01:23 UTC
I agree that the status of bugs for which the only Gerrit change(s) are at a status of Abandoned should not show a status of PATCH_TO_REVIEW. It is deceptive and counter to actually getting the bug resolved. For example, when looking for a bug to start work on would you ever choose to include bugs with the status PATCH_TO_REVIEW in your search results?

The reason for the abandonment is not relevant.  The effective status is that the bug needs the attention of a developer to begin work on a solution. If it happens that there is code which might be adapted or used as a starting point that is something that the developer can determine by reading the bug.

The point is to return such bugs to the point where they are appropriately placed within the Bug management/Bug report life cycle.  The way to do that is to remove the effect that having the abandoned Gerrit change is having on the status of the bug.
Comment 3 Andre Klapper 2014-09-25 20:24:39 UTC
I would not spend too much time thinking about this, because in a few months we will neither have Bugzilla nor Gerrit anymore if all goes well. :)
See https://www.mediawiki.org/wiki/Phabricator

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links