-----Original Message-----
From: <[email protected]> on behalf of Ben Pfaff <[email protected]>
Date: Tuesday, August 1, 2017 at 10:23 AM
To: "[email protected]" <[email protected]>
Subject: [ovs-dev] RFC: Let's branch for 2.8 today

    I'd like to create branch-2.8 today in preparation for releasing OVS 2.8
    later in August.  I sent the patch that would lead off the branch a few
    minutes ago:
            
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_pipermail_ovs-2Ddev_2017-2DAugust_336544.html&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=EHRmZog9ZtlKH5MXuo4OklgP6dlm_pfMwfokiw2bXGk&s=udsL-1fyk8cB7_qe39p2Ua8qSMMWmIcBcWDmsjECPTg&e=
 
    
    According to our published schedule, we should have create branch-2.8 at
    the beginning of July, but we delayed to allow some more features to
    enter the 2.8 release.  There continue to be reasonable arguments along
    these lines in favor of delaying branching further:
    
            * Many DPDK patches have been posted but are still under review
              or awaiting application.

I don’t see much problem for double commit as the baselines should be identical.
However, most DPDK folks are offline until late tonight PST; can we give them a 
chance to be
back online before branching ?

    
            * Multiple series of patches leading up to NSH support have been
              posted but are still iterating through reviews.
    
    The primary argument in favor of branching quickly is to keep to a
    regular release cadence.  My understanding is that multiple downstream
    projects rely on prompt Open vSwitch releases.  (This is mainly based on
    speaking to Russell Bryant at Red Hat; he can fill in the details if
    need be.)  I'd prefer to stick to our schedule for this reason.
    
    I propose that we branch today, with the following further details:
    
            * Continue to apply patches that add features, that as of now
              have already been posted and ready for review or iterating on
              reviews, until approximately this Friday.

For limited scope features, would be ok to allow a little longer, maybe early 
next week ?

  These patches will
              need to be committed both to master and branch-2.8.
    
            * As always, bug fix patches are acceptable on any branch at any
              time.
    
            * Plan to release, given acceptable quality, during the last
              week of August.
    
    Thoughts?
    
    Thanks,
    
    Ben.
    _______________________________________________
    dev mailing list
    [email protected]
    
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=EHRmZog9ZtlKH5MXuo4OklgP6dlm_pfMwfokiw2bXGk&s=9VEWp89QUGpFZt15Xw2A3I7u7X3Le-4H_EGM7Vo7eiU&e=
 
    

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to