[ovs-discuss] questions regarding bug tracking/handling

[Mark Haywood]

Not that I have a bug to report, but I have some bug tracking questions ...

First, is there a public bug tracking tool for tracking bugs against
Open vSwitch LTS releases?

Second, how do security bugs, get reported upstream? Are they reported
on this (bugs at openvswitch.org) alias?

As I understand the FAQ, if a significant bug is identified in an LTS
release, then an updated release will be provided that includes a fix.
Does this mean, for example, that a significant bug in LTS release 2.1.2
would be fixed in an updated LTS release 2.1.3?

Thanks,
Mark



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20141007/83ec8628/attachment-0001.html>

[Ben Pfaff]

Post by Mark Haywood
First, is there a public bug tracking tool for tracking bugs against
Open vSwitch LTS releases?

You can use the github bug tracker for the openvswitch project if you
like.

Post by Mark Haywood
Second, how do security bugs, get reported upstream? Are they
reported on this (bugs at openvswitch.org) alias?

If you think that they are sensitive bugs, then it might be a good
idea to discuss them privately first. We don't have a process or a
specific list for that yet. (We might be able to use the committers
list.) In the absence of such a procedure, if you wanted to email me
about such problems, I'll be happy to help.

Post by Mark Haywood
As I understand the FAQ, if a significant bug is identified in an
LTS release, then an updated release will be provided that includes
a fix. Does this mean, for example, that a significant bug in LTS
release 2.1.2 would be fixed in an updated LTS release 2.1.3?

Yes, that's what we do.