Hi All, At the last OVS-DPDK community sync meeting the issue of bug reporting and tracking was raised. Specifically
1. What is currently available? 2. Are there any improvements that can be made in the process? As it stands the process to follow is defined at: http://docs.openvswitch.org/en/latest/internals/bugs/ An open vSwitch issue tracker repo has already been setup on GitHub at https://github.com/openvswitch/ovs-issues/issues >From what I can see, the GitHub tracker seems to be used infrequently. Not >sure if this is because it's not required to report bugs or that people are >not aware of it? Is there a policy users should follow as regards reporting bugs on GitHub? Many groups will maintain their own internal bug tracking, I'm wondering would it be good practice to have people report known bugs in the GitHub tool? I see the pros and cons as follows: Pros 1. GitHub provides a common location to discuss bugs, this helps avoid duplication of effort as it can be easily flagged if someone is working on a patch for said bug. 2. If used frequently then it will provide an accurate picture of what known issues are outstanding in OVS (easier then trawling through the mailing list). 3. It could be used in conjunction with Patchwork to flag patches for review that are bug fixes. (I've read the patchwork allows a field to link to an external bug report url, I'm open to correction on this). Cons 1. More overhead in general when creating the issue in GitHub when compared to reporting via email to the ML. What do others think? Is their value in formalizing the bug report process to use an external bug tracker? Ian _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
