Re: 3.6.3 bugs are wrongly moved to MODIFIED

David, Is it something manual we need to change per version or we can add something automatic to work on any 3.6.X branch only (exluding the 3.6 branch)?

=20 e. =20 On Thu, Jan 28, 2016 at 4:00 PM, Tal Nisan <tnisan(a)redhat.com&gt; wrote: =20 > This was the behavior in 3.6.2, don't know why it changed > > On Thu, Jan 28, 2016 at 3:57 PM, Eyal Edri <eedri(a)redhat.com&gt; wrote: > >> so maybe we'll stop moving bugs to MODIFIED if they are merged on stab=

>> branch (i.e ovirt-engine-3.6) and only if its merged into a version br=

>> (i.e ovirt-engine-3.6.3) ? >> >> On Thu, Jan 28, 2016 at 3:52 PM, Tal Nisan <tnisan(a)redhat.com&gt; wrote: >> >>> It makes life easier for everyone when automation moves the bug to >>> MODIFIED, if the work is not done then the developer can always move =

>>> back to POST like we sometimes do. >>> In any way, when a 3.6.3 bug is merged in 3.6.3 it should be moved to >>> MODIFIED, not a second before >>> >>> >>> On Thu, Jan 28, 2016 at 12:23 PM, Yedidyah Bar David <didi(a)redhat.com&gt; >>> wrote: >>> >>>> On Thu, Jan 28, 2016 at 10:59 AM, Eyal Edri <eedri(a)redhat.com&gt; wrote: >>>> > >>>> > >>>> > On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David <didi(a)redhat.=

>>>> > >>>> > wrote: >>>> >> >>>> >> On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri <eedri(a)redhat.com&gt; >>>> wrote: >>>> >> > Maybe we should change the logic on moving bugs to MODIFIED, >>>> >> > Now that we moved to the version branch. >>>> >> > >>>> >> > Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED >>>> that >>>> >> > we'll >>>> >> > be sure its OK? >>>> >> >>>> >> Repeating myself from a previous discussion: I think we should ne=

>>>> move >>>> >> bugs from POST to MODIFIED. Only a developer can know if it's ind=

>>>> >> ready, >>>> >> or another patch is still needed but was not yet pushed. I think =

>>>> >> safer >>>> >> to miss bugs left on POST although they could have been moved to >>>> MODIFIED, >>>> >> than the opposite - move to MODIFIED bugs that actually require m=

>>>> work. >>>> >> >>>> > >>>> > You're optimistic that bugs will not stay on POST, we've done it in >>>> the >>>> > past. >>>> > This has a bigger risk of bugs getting left behind on POST and >>>> increasing >>>> > the amount of >>>> > bugs that are not verified on time. >>>> > >>>> > Its the easiest solution to drop this bot, but i belive it will do >>>> more >>>> > damage than good. >>>> >>>> Perhaps, then, run it once a day and move to MODIFIED only if last p=

>>>> was merged at least X hours ago? Hopefully developers will not wait =

>>>> than X before pushing an additional patch for the same bug if needed. >>>> >>>> Of course, we then also have to fix the issue starting current threa=

>>>> >>>> > >>>> >> >>>> >> > >>>> >> > e. >>>> >> > >>>> >> > On Thu, Jan 28, 2016 at 10:03 AM, Tal Nisan <tnisan(a)redhat.com&gt; >>>> wrote: >>>> >> >> >>>> >> >> After merging a patch for a 3.6.3 bug on the ovirt-engine-3.6 >>>> branch >>>> >> >> the >>>> >> >> bug is moved to MODIFIED, since the 3.6.3 branch was opened >>>> yesterday >>>> >> >> the >>>> >> >> bug should stay in POST until merged in ovirt-engine-3.6.3 bra=

>>>> as >>>> >> >> well >>>> >> >> >>>> >> >> >>>> >> >> _______________________________________________ >>>> >> >> Infra mailing list >>>> >> >> Infra(a)ovirt.org >>>> >> >> http://lists.ovirt.org/mailman/listinfo/infra >>>> >> >> >>>> >> > >>>> >> > >>>> >> > >>>> >> > -- >>>> >> > Eyal Edri >>>> >> > Associate Manager >>>> >> > EMEA ENG Virtualization R&D >>>> >> > Red Hat Israel >>>> >> > >>>> >> > phone: +972-9-7692018 >>>> >> > irc: eedri (on #tlv #rhev-dev #rhev-integ) >>>> >> > >>>> >> > _______________________________________________ >>>> >> > Infra mailing list >>>> >> > Infra(a)ovirt.org >>>> >> > http://lists.ovirt.org/mailman/listinfo/infra >>>> >> > >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Didi >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > Eyal Edri >>>> > Associate Manager >>>> > EMEA ENG Virtualization R&D >>>> > Red Hat Israel >>>> > >>>> > phone: +972-9-7692018 >>>> > irc: eedri (on #tlv #rhev-dev #rhev-integ) >>>> >>>> >>>> >>>> -- >>>> Didi >>>> >>> >>> >> >> >> -- >> Eyal Edri >> Associate Manager >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > > =20 =20 --=20 Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel =20 phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWsOUhAAoJEEBxx+HSYmnDKqIH/RjqeEgHXC4OuKIM6t2M36ge oBW226IzslN9fqkdJBrwC6zmEOoX5G7DgvNOo0Lths/Y2lijuLgPcecU8ralFXs/ ePAK/0OE6k9oR8gn3sYzBUurgrC9SzxF+/FrtHv8Bj0FFvVDaSI12uY81FGvumCN HAQzd31ZXo2eTIXiLsQYduvSFhgmQZrtlVo67pIYTve0TJfgIHGExIE9N8WhDsn/ MEwpaNLeFHjyiHtHSvwY+v0UvoAFr+c/m6OBVSmoFWG0dHkJvUMLEYnP19enLwDD /1Ck38AJzmDziwHPMFxT+k0BAv5wG8TYeVYBMJBkzivjgOw7UZRRxy48qfSgGKY= =weAi -----END PGP SIGNATURE-----