On Fri, Feb 19, 2016 at 9:21 AM, David Causse <[email protected]> wrote: > Le 18/02/2016 20:28, Guillaume Lederrey a écrit : >> >> On Thu, Feb 18, 2016 at 7:48 PM, Stas Malyshev <[email protected]> >> wrote: >>> >>> Hi! >>> >>>> T109101 is actually done, but waiting for the elasticsearch upgrade to >>>> push it at the same time to prod (to do only one restart). This is >>>> still WiP, so I dont want to close it, but it is not really in need of >>>> review either. >>> >>> I would put it to Done column and make a note inside the task that it is >>> waiting for being deployed, so nobody resolves it. Then when it's >>> deployed it can be actually resolved. >> >> If this is only an isolated use case, and most of the time this does >> not happen, I would agree with you. If it is something that happens >> regularly (and I can see myself having this regularly, not sure if it >> will really be the case) I think this is work in progress that will be >> hidden in a "done" column and I don't like it. One of the important >> role of a Kanban, is to surface where we have WiP stuck. I am most >> probably biased by my previous experiences, but waiting for deployment >> is a place where I could see things accumulate... > > > It's what is done by the analytics team: > https://phabricator.wikimedia.org/project/view/1030/ > with a "Ready to Deploy" column. I don't have any objection to add a new > column.
Let's wait and if I have more than one task to put there. But if it is the case, I think it could be a good solution. > > > _______________________________________________ > discovery mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/discovery _______________________________________________ discovery mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/discovery
