Re: [openstack-dev] [Fuel] Aligning LP groups with real teams
Hi, just wanted to let you know that fuel-astute and fuel-provisioning groups have been removed from LP. BTW, any chance we can somehow to reduce spam emails when some bug was assigned to another team? Igor, I'd recommend to setup email filters and lables. There are messages like You received this bug notification because you are a member of Fuel for Openstack, which is a bug assignee or You received this bug notification because you are a member of Fuel Library Team, which is a bug assignee. So you can direct such emails into different folders/labels. Regards, Alex On Fri, Jul 17, 2015 at 4:26 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: Hello, Here's my +2 on this. :) BTW, any chance we can somehow to reduce spam emails when some bug was assigned to another team? For instance, I see email notifications when bug's assigned to fuel-library. Thanks, Igor On Fri, Jul 17, 2015 at 4:16 PM, Tatyana Leontovich tleontov...@mirantis.com wrote: Hi, Alex vote +1 to use astute tag as well to get possibility identify issues related to astute in the most easy way. Regards, Tanya On Fri, Jul 17, 2015 at 3:59 PM, Aleksandr Didenko adide...@mirantis.com wrote: Hi, as we decided on the recent Fuel weekly IRC meeting, we need to align LP fuel-* groups with our teams and bug confirmation queues/duties. We decided to start with fuel-astute [0] and fuel-provsioning [1] LP groups that have 2 members each. So from now on please assign bugs about provisioning and astute to fuel-python [2] LP gorup and add 'ibp' tag for bugs about provisioning. Guys from fuel-python, please pay attention to bug tags. If you're the SME for 'ibp', please take a look at 'ibp' bugs first. Btw should we also use 'astute' tag for the same purpose? Also we need someone to delete fuel-astute and fuel-provisioning groups from LP, if there are no objections. Regards, Alex [0] https://launchpad.net/~fuel-astute/+members#active [1] https://launchpad.net/~fuel-provisioning/+members#active [2] https://launchpad.net/~fuel-python/+members#active __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Aligning LP groups with real teams
Hello, Here's my +2 on this. :) BTW, any chance we can somehow to reduce spam emails when some bug was assigned to another team? For instance, I see email notifications when bug's assigned to fuel-library. Thanks, Igor On Fri, Jul 17, 2015 at 4:16 PM, Tatyana Leontovich tleontov...@mirantis.com wrote: Hi, Alex vote +1 to use astute tag as well to get possibility identify issues related to astute in the most easy way. Regards, Tanya On Fri, Jul 17, 2015 at 3:59 PM, Aleksandr Didenko adide...@mirantis.com wrote: Hi, as we decided on the recent Fuel weekly IRC meeting, we need to align LP fuel-* groups with our teams and bug confirmation queues/duties. We decided to start with fuel-astute [0] and fuel-provsioning [1] LP groups that have 2 members each. So from now on please assign bugs about provisioning and astute to fuel-python [2] LP gorup and add 'ibp' tag for bugs about provisioning. Guys from fuel-python, please pay attention to bug tags. If you're the SME for 'ibp', please take a look at 'ibp' bugs first. Btw should we also use 'astute' tag for the same purpose? Also we need someone to delete fuel-astute and fuel-provisioning groups from LP, if there are no objections. Regards, Alex [0] https://launchpad.net/~fuel-astute/+members#active [1] https://launchpad.net/~fuel-provisioning/+members#active [2] https://launchpad.net/~fuel-python/+members#active __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Fuel] Aligning LP groups with real teams
Hi, as we decided on the recent Fuel weekly IRC meeting, we need to align LP fuel-* groups with our teams and bug confirmation queues/duties. We decided to start with fuel-astute [0] and fuel-provsioning [1] LP groups that have 2 members each. So from now on please assign bugs about provisioning and astute to fuel-python [2] LP gorup and add 'ibp' tag for bugs about provisioning. Guys from fuel-python, please pay attention to bug tags. If you're the SME for 'ibp', please take a look at 'ibp' bugs first. Btw should we also use 'astute' tag for the same purpose? Also we need someone to delete fuel-astute and fuel-provisioning groups from LP, if there are no objections. Regards, Alex [0] https://launchpad.net/~fuel-astute/+members#active [1] https://launchpad.net/~fuel-provisioning/+members#active [2] https://launchpad.net/~fuel-python/+members#active __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] Aligning LP groups with real teams
Hi, Alex vote +1 to use astute tag as well to get possibility identify issues related to astute in the most easy way. Regards, Tanya On Fri, Jul 17, 2015 at 3:59 PM, Aleksandr Didenko adide...@mirantis.com wrote: Hi, as we decided on the recent Fuel weekly IRC meeting, we need to align LP fuel-* groups with our teams and bug confirmation queues/duties. We decided to start with fuel-astute [0] and fuel-provsioning [1] LP groups that have 2 members each. So from now on please assign bugs about provisioning and astute to fuel-python [2] LP gorup and add 'ibp' tag for bugs about provisioning. Guys from fuel-python, please pay attention to bug tags. If you're the SME for 'ibp', please take a look at 'ibp' bugs first. Btw should we also use 'astute' tag for the same purpose? Also we need someone to delete fuel-astute and fuel-provisioning groups from LP, if there are no objections. Regards, Alex [0] https://launchpad.net/~fuel-astute/+members#active [1] https://launchpad.net/~fuel-provisioning/+members#active [2] https://launchpad.net/~fuel-python/+members#active __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
