[ovs-dev] RFC: two-week feature freeze on master before branching
Ryan Moats
rmoats at us.ibm.com
Sat Jul 30 11:46:46 UTC 2016
"dev" <dev-bounces at openvswitch.org> wrote on 07/29/2016 11:55:13 PM:
> From: Ben Pfaff <blp at ovn.org>
> To: dev at openvswitch.org
> Date: 07/29/2016 11:55 PM
> Subject: [ovs-dev] RFC: two-week feature freeze on master before
branching
> Sent by: "dev" <dev-bounces at openvswitch.org>
>
> We've done a good job of getting our features into master before
> branching for the 2.6 release on the proposed date of Aug. 1. Thanks,
> everybody. However, I know that some features targeted at 2.6 will be
> coming in next week, because various developers have already mentioned
> this. This means that we'll end up doing a fair amount of backporting.
>
> Therefore, I want to propose an experiment of changing our process for
> this release. If the experiment works out, we can consider doing the
> same thing for later releases. My proposal is this:
>
> - From Aug. 1 to Aug. 15, accept for master only bug fixes and
> features already announced as targeted at 2.6.
>
> - On Aug. 15, create the branch whatever is on master at the time.
>
> - After Aug. 15, accept only bug fixes for 2.6 and un-freeze master.
>
> Comments appreciated.
>
> Thanks,
>
> Ben.
Sounds like a reasonable thing to try and see how it works.
Ryan
More information about the dev
mailing list