Open Stack

I'm not sure what the guideline is, but I would like to point out a good
reason to have the bug report even for obvious fixes.
When users encounters bugs, they go to launchpad to report them. They don't
first scan the commits of the master branch to see what was fixed. Having
the bug in launchpad provides a way to track the status (fixed, backported,
impact, etc) of the bug and reduces the chances of duplicated bugs.

Can you provide an example of a patch that you felt was trivial that a
reviewer requested a bug for so we have something concrete to discuss and
establish guidelines around?
On Aug 13, 2014 12:32 AM, "Angus Lees" <gus at inodes.org> wrote:

> I'm doing various small cleanup changes as I explore the neutron codebase.
> Some of these cleanups are to fix actual bugs discovered in the code.
>  Almost
> all of them are tiny and "obviously correct".
>
> A recurring reviewer comment is that the change should have had an
> accompanying bug report and that they would rather that change was not
> submitted without one (or at least, they've -1'ed my change).
>
> I often didn't discover these issues by encountering an actual production
> issue so I'm unsure what to include in the bug report other than basically
> a
> copy of the change description.  I also haven't worked out the pattern yet
> of
> which changes should have a bug and which don't need one.
>
> There's a section describing blueprints in NeutronDevelopment but nothing
> on
> bugs.  It would be great if someone who understands the nuances here could
> add
> some words on when to file bugs:
> Which type of changes should have accompanying bug reports?
> What is the purpose of that bug, and what should it contain?
>
> --
> Thanks,
>  - Gus
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140813/59362373/attachment.html>