[JIRA] (OVIRT-1089) [gerrit hooks] wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David closed OVIRT-1089. --- Resolution: Fixed > [gerrit hooks] wrong target milestone bugs should be blocked with -verified > on the stable branches > -- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.747.0#100028) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) [gerrit hooks] wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26616#comment-26616 ] Shlomo Ben David commented on OVIRT-1089: - patch #[71597|https://gerrit.ovirt.org/#/c/71597] is ready. current status: waiting for CR > [gerrit hooks] wrong target milestone bugs should be blocked with -verified > on the stable branches > -- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.6#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) [gerrit hooks] wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David updated OVIRT-1089: Status: In Progress (was: To Do) > [gerrit hooks] wrong target milestone bugs should be blocked with -verified > on the stable branches > -- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.6#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) [gerrit hooks] wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David updated OVIRT-1089: Summary: [gerrit hooks] wrong target milestone bugs should be blocked with -verified on the stable branches (was: Re: Wrong target milestone bugs should be blocked with -verified on the stable branches) > [gerrit hooks] wrong target milestone bugs should be blocked with -verified > on the stable branches > -- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.4#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26437#comment-26437 ] Tal Nisan commented on OVIRT-1089: -- I will, I'm dedicated to make my life as a stable branch maintainer easier, thanks for that ;) On Mon, Jan 30, 2017 at 3:34 PM, Eyal Edri wrote: > +1, thanks. > > Please continue to let us know if we need to enforce other hooks more > strictly as well :) > > On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan wrote: > >> Yeah I've noticed the hook identified the situation, I'm asking you to >> make it more stricter, hence the email :) >> >> On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: >> >>> It already WARN on it: >>> >>>- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >>> >>> We can make it more strict and give VERIFY -1. >>> Adding infra-support to open a ticket on it. >>> >>> We intentionally didn't enforce Verify as default since we wanted to >>> give time to the hook >>> to work and see we don't have false positives on it. >>> >>> >>> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: >>> >>>> Example: >>>> https://gerrit.ovirt.org/#/c/71374/ >>>> >>>> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >>>> pushed into the 4.1 stable branch >>>> >>>> Thanks. >>>> >>>> ___ >>>> Infra mailing list >>>> Infra@ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/infra >>>> >>>> >>> >>> >>> -- >>> Eyal Edri >>> Associate Manager >>> RHV DevOps >>> EMEA ENG Virtualization R&D >>> Red Hat Israel >>> >>> phone: +972-9-7692018 <+972%209-769-2018> >>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>> >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > Re: Wrong target milestone bugs should be blocked with -verified on the > stable branches > --- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
I will, I'm dedicated to make my life as a stable branch maintainer easier, thanks for that ;) On Mon, Jan 30, 2017 at 3:34 PM, Eyal Edri wrote: > +1, thanks. > > Please continue to let us know if we need to enforce other hooks more > strictly as well :) > > On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan wrote: > >> Yeah I've noticed the hook identified the situation, I'm asking you to >> make it more stricter, hence the email :) >> >> On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: >> >>> It already WARN on it: >>> >>>- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >>> >>> We can make it more strict and give VERIFY -1. >>> Adding infra-support to open a ticket on it. >>> >>> We intentionally didn't enforce Verify as default since we wanted to >>> give time to the hook >>> to work and see we don't have false positives on it. >>> >>> >>> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: >>> Example: https://gerrit.ovirt.org/#/c/71374/ I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is pushed into the 4.1 stable branch Thanks. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra >>> >>> >>> -- >>> Eyal Edri >>> Associate Manager >>> RHV DevOps >>> EMEA ENG Virtualization R&D >>> Red Hat Israel >>> >>> phone: +972-9-7692018 <+972%209-769-2018> >>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>> >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26436#comment-26436 ] eyal edri [Administrator] commented on OVIRT-1089: -- +1, thanks. Please continue to let us know if we need to enforce other hooks more strictly as well :) On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan wrote: > Yeah I've noticed the hook identified the situation, I'm asking you to > make it more stricter, hence the email :) > > On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: > >> It already WARN on it: >> >>- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >> >> We can make it more strict and give VERIFY -1. >> Adding infra-support to open a ticket on it. >> >> We intentionally didn't enforce Verify as default since we wanted to give >> time to the hook >> to work and see we don't have false positives on it. >> >> >> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: >> >>> Example: >>> https://gerrit.ovirt.org/#/c/71374/ >>> >>> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >>> pushed into the 4.1 stable branch >>> >>> Thanks. >>> >>> ___ >>> Infra mailing list >>> Infra@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/infra >>> >>> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Re: Wrong target milestone bugs should be blocked with -verified on the > stable branches > --- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
+1, thanks. Please continue to let us know if we need to enforce other hooks more strictly as well :) On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan wrote: > Yeah I've noticed the hook identified the situation, I'm asking you to > make it more stricter, hence the email :) > > On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: > >> It already WARN on it: >> >>- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >> >> We can make it more strict and give VERIFY -1. >> Adding infra-support to open a ticket on it. >> >> We intentionally didn't enforce Verify as default since we wanted to give >> time to the hook >> to work and see we don't have false positives on it. >> >> >> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: >> >>> Example: >>> https://gerrit.ovirt.org/#/c/71374/ >>> >>> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >>> pushed into the 4.1 stable branch >>> >>> Thanks. >>> >>> ___ >>> Infra mailing list >>> Infra@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/infra >>> >>> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26435#comment-26435 ] Tal Nisan commented on OVIRT-1089: -- Yeah I've noticed the hook identified the situation, I'm asking you to make it more stricter, hence the email :) On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: > It already WARN on it: > >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > > > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > >> Example: >> https://gerrit.ovirt.org/#/c/71374/ >> >> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >> pushed into the 4.1 stable branch >> >> Thanks. >> >> ___ >> Infra mailing list >> Infra@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > Re: Wrong target milestone bugs should be blocked with -verified on the > stable branches > --- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
Yeah I've noticed the hook identified the situation, I'm asking you to make it more stricter, hence the email :) On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri wrote: > It already WARN on it: > >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > > > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > >> Example: >> https://gerrit.ovirt.org/#/c/71374/ >> >> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >> pushed into the 4.1 stable branch >> >> Thanks. >> >> ___ >> Infra mailing list >> Infra@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-1089: Assignee: Shlomo Ben David (was: infra) > Re: Wrong target milestone bugs should be blocked with -verified on the > stable branches > --- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: Shlomo Ben David > > It already WARN on it: >- Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > ___ > > Infra mailing list > > Infra@ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
eyal edri [Administrator] created OVIRT-1089: Summary: Re: Wrong target milestone bugs should be blocked with -verified on the stable branches Key: OVIRT-1089 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra It already WARN on it: - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 We can make it more strict and give VERIFY -1. Adding infra-support to open a ticket on it. We intentionally didn't enforce Verify as default since we wanted to give time to the hook to work and see we don't have false positives on it. On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > Example: > https://gerrit.ovirt.org/#/c/71374/ > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > pushed into the 4.1 stable branch > > Thanks. > > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
It already WARN on it: - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 We can make it more strict and give VERIFY -1. Adding infra-support to open a ticket on it. We intentionally didn't enforce Verify as default since we wanted to give time to the hook to work and see we don't have false positives on it. On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan wrote: > Example: > https://gerrit.ovirt.org/#/c/71374/ > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > pushed into the 4.1 stable branch > > Thanks. > > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Wrong target milestone bugs should be blocked with -verified on the stable branches
Example: https://gerrit.ovirt.org/#/c/71374/ I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is pushed into the 4.1 stable branch Thanks. ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
