Re: automation wrongly moving bugs to MODIFIED

On Tue, Nov 17, 2015 at 10:54 AM, Eyal Edri <eedri(a)redhat.com&gt; wrote: > indeed. > we need to decide here what automation we want (each flow has its cons & > pros) > > moving bugs from POST->MODIFIED > - pros > - bugs are not forgotten on POST and waiting for manual action, > leaving possibility of not moving to ON_QA on a release even though they are > fixed. I think it's still a bit risky and should be left for a human. At least as long as we do not do TDD. > > - cons > - bot can't know if bug is solved completely and more patches are > coming. > > > solution: > - use bug-url ONLY in the main patch that when its merged then > bug will move to MODIFIED, all other patches should use related-to: (we can > ensure bug won't change status for related to patches) I can live with this, but as I wrote in another mail in this thread, I think that's a bit overloading the meaning of Related-To. > > > moving MODIFIED->POST > - i think in any case we should stop doing this, and its the > maintainer responsibility to move it back to POST if he didn't add all > patches. Really? Do you see any risk in moving to POST?

-- Didi