On 3/17/2016 11:41 AM, Markus Zoeller wrote:
What are the various reasons which block you to work on bug reports? This question goes especially to the new contributors but also to the rest of us. For me, personally, it's that most bug reports miss the steps to reproduce which allow me to see the issue on my local system before I start to dig into the code. I'm asking this because I'm not sure what the main reasons are that our bug list is this huge (~1000 open bug reports). Maybe you have reasons which can be resolved or mitigated by me in my bug czar role. Let me know. Regards, Markus Zoeller (markus_z) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Clear recreate steps is probably #1, but also logs if there are obvious failures. A stacktrace goes a long way with a clear description of the failure scenario. Obviously need to know the level of code being tested.
For a lot of bugs that are opened on n-2 releases, like kilo at this point, my first question is, have you tried this on master to see if it's still an issue. That's lazy on my part, but it's easy if I'm not aware of a fix that just needs backporting.
-- Thanks, Matt Riedemann __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
