On Mon, Apr 11, 2016 at 06:58:42PM -0700, Han Zhou wrote: > On Mon, Apr 11, 2016 at 3:57 PM, Ben Pfaff <b...@ovn.org> wrote: > > > > [dropping some CCs for people I know to be on ovs-dev] > > > > On Sun, Apr 10, 2016 at 08:45:38PM -0700, Han Zhou wrote: > > > As requested by several folks and also mentioned in last week's ovn > > > meeting, we would like this repo to be hosted publicly under > > > https://github.com/openvswitch/ so that more people in the community can > > > contribute and benefit from it. Or it could be a folder under ovs repo, > > > e.g. ovn/scale-test. The goal is to be able to enable regular regression > > > test for scalability of ovn, so that we are aware of impact introduced > by > > > changes. > > > > Which possibility do you like better? As I see it, here are some > > advantages and disadvantages of each approach. > > > > Probably, it is easier to quickly evolve the scale-test in a separate > > repo, because for something that is quickly evolving OVS (as you know) > > has a relatively heavyweight and slow review process. I don't know > > whether this is important. > > > > Probably, it will be easier to keep the scale test in sync with OVS and > > OVN if it is in the same repository, because devs will be more likely to > > see it as they work on OVN. I don't know whether this is important > > either. > > Ben, I agree with your considerations but have no preference yet. Would > like to hear opinion from other folks. If we use separate repo, should it > still be the same review & merge process like the ovs repo?
If we use a separate repo, it's up to the contributors to decide on the review process. Anything that they agree to is fine. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
