Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 13/08/14 09:28, Angus Lees 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?
> 

It was discussed before at:
http://lists.openstack.org/pipermail/openstack-dev/2014-May/035789.html

/Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQEcBAEBCgAGBQJT6zfOAAoJEC5aWaUY1u570wQIAMpoXIK/p5invp+GW0aMMUK0
C/MR6WIJ83e6e2tOVUrxheK6bncVvidOI4EWGW1xzP1sg9q+8Hs1TNyKHXhJAb+I
c435MMHWsDwj6p1OeDxHnSOVMthcGH96sgRa1+CIk6+oktDF3IMmiOPRkxdpqWCZ
7TkV75mryehrTNwAkVPfpWG3OhWO44d5lLnJFCIMCuOw2NHzyLIOoGQAlWNQpy4V
a869s00WO37GEed6A5Zizc9K/05/6kpDIQVim37tw91JcZ69VelUlZ1THx+RTd33
92r87APm3fC/LioKN3fq1UUo2c94Vzl3gYPFVl8ZateQNMKB7ONMBePOfWR9H1k=
=wCJQ
-----END PGP SIGNATURE-----