Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

actice Best regards, Hongbin From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: September-17-15 5:09 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me) For posterity, I h

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me) For posterity, I have recorded this guidance in our Contributing Wiki: See the NOTE section under: https://wiki.openstack.org/wiki/Magnum/Contributing

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

I agree. Lots of projects have this issue. I submitted a bug fix once that literally was 3 characters long, and it took: A short commit message, a long commit message, and a full bug report being filed and cross linked. The amount of time writing it up was orders of magnitude longer then the

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

On Thu, Sep 17, 2015 at 3:28 PM, Fox, Kevin M wrote: > I agree. Lots of projects have this issue. I submitted a bug fix once that > literally was 3 characters long, and it took: > A short commit message, a long commit message, and a full bug report being > filed and cross

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

On Thu, Sep 17, 2015 at 4:09 PM, Jeff Peeler wrote: > > On Thu, Sep 17, 2015 at 3:28 PM, Fox, Kevin M wrote: > >> I agree. Lots of projects have this issue. I submitted a bug fix once >> that literally was 3 characters long, and it took: >> A short commit

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

Let’s apply sensible reason. If it’s a new feature or a bug, it should be tracked against an artifact like a bug ticket or a blueprint. If it’s truly trivia, we don’t care. I can tell you that some of the worst bugs I have ever seen in my career had fixes that were about 4 bytes long. That did

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

For posterity, I have recorded this guidance in our Contributing Wiki: See the NOTE section under: https://wiki.openstack.org/wiki/Magnum/Contributing#Identify_bugs Excerpt: "NOTE: If you are fixing something trivial, that is not actually a functional defect in the software, you can do that