Hi Ben, Ben Pfaff <b...@ovn.org> writes:
> This document has two different kinds of text: > > - The first sections of the document, "Release Strategy" and "Release > Numbering", describe what we've already been doing for most of the > history of Open vSwitch. If there is anything surprising in them, > then it's because our process has not been transparent enough, and not > because we're making a change. > > - The final section of the document, "Release Scheduling", is a proposal > for current and future releases. We have not had a regular release > schedule in the past, but it seems important to have one in the > future, so this section requires review and feedback from everyone in > the community. > > Signed-off-by: Ben Pfaff <b...@ovn.org> > --- I like the document overall. Two things that may or may not need clarification: 1. Consensus is mentioned multiple times - is it expected that this discussion would take place on ovs-dev? I haven't seen it happen on announce, dev, or discuss (though I'll admit I only went through them briefly). The only other time consensus is discussed in the documentation for ovs is under SECURITY.md, where the mailing list for such discussion takes place, and participation criteria, etc. 2. For the mentioned case of features close to the branch date, what is the protocol for getting them in? Again it was consensus, but is the approach to simply mail ovs-dev with "[backport]" tag identifying the upstream commits? Should we state that in the submissions if we're close to the deadline (I just submitted two series close to the branch deadline, so I'm more interested in this answer). Otherwise, I really like the cadence outlined, and the prose flows well. Thanks, -Aaron _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
