[openstack-dev] [Fuel] Duplicate bugs vs reopening unrelated bugs
aurlapova at mirantis.com
Thu Nov 20 15:06:00 UTC 2014
thank you that you raised this important discussion and added section @Test
and report bug.
>From my side I want notice, that we have many unclear bugs and sometimes is
very hard to verify such bugs.
The awesome example: https://bugs.launchpad.net/fuel/+bug/1357298
there are many questions about verification:
- env/iso version
- why this option @haven't be used here
- where is it should be
and so on.
Discussion about issue template you can find in community @[openstack-dev] [
QA] Proposal: A launchpad bug description template
will be great if we will use such template in our launchpad at least as
good practice while it are integrating in community.
On Wed, Nov 19, 2014 at 4:30 AM, Dmitry Borodaenko <dborodaenko at mirantis.com
> I've added the following paragraph into Fuel's How to contribute Wiki page:
> "Before creating a new bug, it's always a good idea to check if a bug
> like that already exists in the project, and update an existing bug
> instead of creating something that will later have to be discarded as
> a duplicate. However, it is important to make sure that both bugs are
> really related, dealing with a duplicate is much easier than
> untangling several unrelated lines of investigation mixed into one
> bug. Do not ever reopen bugs with generic catch-all titles like
> "Horizon crashed" or "HA doesn't work" that can cover whole ranges of
> root causes. Do not create new bugs with such titles, either: be as
> specific about the nature of the problem as you can."
> Overly generic bugs and the related problem of reopening or hijacking
> unrelated bugs has been an anti-pattern in our Launchpad bugs lately,
> please take above into consideration when reporting bugs.
> Thank you,
> Dmitry Borodaenko
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev