Last modified: 2013-08-02 19:38:53 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 T52842, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50842 - Add "Work in progress" button/status to Gerrit workflow to reduce dashboard noise
Add "Work in progress" button/status to Gerrit workflow to reduce dashboard n...
Status: REOPENED
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-05 22:30 UTC by Carl Fürstenberg
Modified: 2013-08-02 19:38 UTC (History)
10 users (show)

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


Attachments
Screenshot from http://i.imgur.com/M8XXMPu.png (50.37 KB, image/png)
2013-07-31 20:39 UTC, MZMcBride
Details

Description Carl Fürstenberg 2013-07-05 22:30:32 UTC
On openracks Gerrit, they have a "Work in Progress" button. I'm not 100% sure the workflow, but I think we should have a "Work in progress" button as well.

Obligatory screenshot: http://i.imgur.com/M8XXMPu.png
Comment 1 christian 2013-07-06 07:31:13 UTC
I am all for new, shiny buttons—yay buttons!—but what problem does the
"Work in Progress"-button solve, or is there a use case?


--
Just to have that here as well, and I'll forget otherwise:
Coincidently, just yesterday someone from openstack started a discussion in
#gerrit about their WiP button. There seems to be a related upstream change,
  https://gerrit-review.googlesource.com/#/c/36091/1
which openstack wants to get into upstream. Upstream does not like that change,
and suggests to use labels instead.

(2013-07-06 ~16:31–20:40 UTC. Logs on
  http://echelog.com/logs/browse/gerrit/1372975200
does not show that part yet.)
Comment 2 p858snake 2013-07-06 09:25:34 UTC
(In reply to comment #1)
> I am all for new, shiny buttons—yay buttons!—but what problem does the
> "Work in Progress"-button solve, or is there a use case?

Wild guess, But probably marks it to prevent merging or something.
Comment 3 Andre Klapper 2013-07-08 09:28:22 UTC
New feature => "enhancement" severity
Comment 4 Chad H. 2013-07-31 19:00:06 UTC
If memory serves, it relies on some hacks to their code that haven't made it into upstream. There was some discussion upstream awhile back, but I remember nobody being particularly interested in seeing it through.

I'm going to wontfix, social conventions work just fine here. If you don't want something to merge, provide a negative review of sorts or indicate it in the commit message.
Comment 5 MZMcBride 2013-07-31 20:22:54 UTC
(In reply to comment #1)
> I am all for new, shiny buttons—yay buttons!—but what problem does the
> "Work in Progress"-button solve, or is there a use case?

I'm not sure about a button, but the underlying goal here is to prevent dashboards/queues from the added noise of "draft changes"/"[WIP]" changes.

Re-opening this for further consideration with a clarified bug summary.
Comment 6 MZMcBride 2013-07-31 20:39:25 UTC
Created attachment 13039 [details]
Screenshot from http://i.imgur.com/M8XXMPu.png

Please upload screenshots and other bug-related media to Bugzilla as attachments. imgur auto-prunes; Bugzilla does not. :-)

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


Navigation
Links