Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru On Jun 17, 2014, at 2:27 PM, Sylvain Bauza sba...@redhat.com wrote: Hi, There is an action for creating a Gerrit dashboard to show all NFV-related specs and patches. As it requires to have a specific label for discriminating them, I'm adding NFVImpact in all the patches proposed in [1]. The side effect is that it creates another patchset and so runs another Jenkins check so don't worry about it. I'll do a team status by tomorrow but meanwhile, please make sure that if you upload a new patch to Gerrit, it will be marked as NFVImpact in the commit message. Many thanks, -Sylvain [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
Yeh, this seems incredibly poluting, don't do this. That's not something I want in our long term git history without conversation about the policy. Every other Impact flag that we use in OpenStack had a pretty long conversation about it's addition. The issue arrises because the NFV team has created *so* many blueprints that they believe are critical to them that it creates a query string too long for browsers to handle. Which I think is it's own issue. I'm liable to start -1ing for commit message pollution if I see this tag. Especially as a bunch of the NFV related features that got jammed through on feature freeze without sufficient testing are currently now breaking (as one would expect without sufficient testing). So I feel this project management dashboard / drum beat is not serving anyone well. Not OpenStack, not the NFV team, not anyone. -Sean On 10/29/2014 06:25 AM, Maru Newby wrote: Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru On Jun 17, 2014, at 2:27 PM, Sylvain Bauza sba...@redhat.com wrote: Hi, There is an action for creating a Gerrit dashboard to show all NFV-related specs and patches. As it requires to have a specific label for discriminating them, I'm adding NFVImpact in all the patches proposed in [1]. The side effect is that it creates another patchset and so runs another Jenkins check so don't worry about it. I'll do a team status by tomorrow but meanwhile, please make sure that if you upload a new patch to Gerrit, it will be marked as NFVImpact in the commit message. Many thanks, -Sylvain [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
- Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve On Jun 17, 2014, at 2:27 PM, Sylvain Bauza sba...@redhat.com wrote: Hi, There is an action for creating a Gerrit dashboard to show all NFV-related specs and patches. As it requires to have a specific label for discriminating them, I'm adding NFVImpact in all the patches proposed in [1]. The side effect is that it creates another patchset and so runs another Jenkins check so don't worry about it. I'll do a team status by tomorrow but meanwhile, please make sure that if you upload a new patch to Gerrit, it will be marked as NFVImpact in the commit message. Many thanks, -Sylvain [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
On 10/29/2014 07:25 AM, Steve Gordon wrote: - Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve Steve, et all, sorry for piling on. I didn't read dates earlier than Maru's post. Glad there is a different solution here. -Sean -- Sean Dague http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
On Oct 29, 2014, at 12:25 PM, Steve Gordon sgor...@redhat.com wrote: - Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve I had a mail filter applied when I looked at the list this morning and I failed to notice that this was an old thread until I had already sent my reply. That said, we have Neutron specs up for review that still include this tag in the commit message and now I know at least that I can ask for their removal. Maru On Jun 17, 2014, at 2:27 PM, Sylvain Bauza sba...@redhat.com wrote: Hi, There is an action for creating a Gerrit dashboard to show all NFV-related specs and patches. As it requires to have a specific label for discriminating them, I'm adding NFVImpact in all the patches proposed in [1]. The side effect is that it creates another patchset and so runs another Jenkins check so don't worry about it. I'll do a team status by tomorrow but meanwhile, please make sure that if you upload a new patch to Gerrit, it will be marked as NFVImpact in the commit message. Many thanks, -Sylvain [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Steve Gordon, RHCE Sr. Technical Product Manager, Red Hat Enterprise Linux OpenStack Platform ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
- Original Message - From: Sean Dague s...@dague.net To: openstack-dev@lists.openstack.org On 10/29/2014 07:25 AM, Steve Gordon wrote: - Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve Steve, et all, sorry for piling on. I didn't read dates earlier than Maru's post. Glad there is a different solution here. -Sean We pretty quickly came to basically the same conclusion as you and Maru are suggesting [1], that doing this was too invasive and created unnecessary noise. Thanks, Steve [1] http://eavesdrop.openstack.org/meetings/nfv/2014/nfv.2014-06-18-14.03.log.html ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [NFV] Patches tagging with NFVImpact
- Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org On Oct 29, 2014, at 12:25 PM, Steve Gordon sgor...@redhat.com wrote: - Original Message - From: Maru Newby ma...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Am I the only one wondering whether introducing arbitrary tagging into our commit messages sets a bad precedent? Or was there a discussion on this topic that I missed? Maru Any particular reason for digging this up from June? We already changed the process so that we did not need to do this. Thanks, Steve I had a mail filter applied when I looked at the list this morning and I failed to notice that this was an old thread until I had already sent my reply. That said, we have Neutron specs up for review that still include this tag in the commit message and now I know at least that I can ask for their removal. Maru Yes, I was thinking after replying that some of the proposals still in flight are quite old and may still have the tag. It can and should be removed. Thanks, Steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [NFV] Patches tagging with NFVImpact
Hi, There is an action for creating a Gerrit dashboard to show all NFV-related specs and patches. As it requires to have a specific label for discriminating them, I'm adding NFVImpact in all the patches proposed in [1]. The side effect is that it creates another patchset and so runs another Jenkins check so don't worry about it. I'll do a team status by tomorrow but meanwhile, please make sure that if you upload a new patch to Gerrit, it will be marked as NFVImpact in the commit message. Many thanks, -Sylvain [1] https://wiki.openstack.org/wiki/Teams/NFV#Active_Blueprints ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
