Re: [ovs-dev] master now "frozen" for forking

[Miguel Angel Ajo Pelayo]

It actually makes a lot of sense.

Please ignore my other comment on master about having the IPv6 RA patch on
2.9,
doing it this way, we effectively have it already.


On Fri, Jan 5, 2018 at 5:51 PM Ben Pfaff  wrote:

> On Fri, Jan 05, 2018 at 03:58:08PM +, Stokes, Ian wrote:
> > > Hello everyone.  We are at the point in the release cycle where
> > > traditionally we would fork a branch from master for release.  We have
> > > tried a slightly different approach a few times and I'd like to propose
> > > that we do it again.  Instead of forking immediately, I propose that we
> > > "freeze" master so that only bug fixes and previously posted feature
> > > enhancements go in, until approximately January 15, and then fork
> > > branch-2.9 from master.  Unless anyone has a serious objection, let's
> do
> > > this.
> >
> > Hi Ben,
> >
> > Am I right in think that cut off for feature enhancements previously
> > discussed on the ML is now January 15th if the above proposal goes
> > ahead?
> >
> > I guess there was an assumption on the OVS DPDK side that we would
> > branch on January 1st with bug fixes and previously discussed feature
> > enhancements possible until end of January for the 2.9 release,
> > official release of 2.9 then being February 15th?
>
> That's still roughly correct.  The main difference here is that, until
> Jan. 15 or so, we're applying the rules that will be used for branch-2.9
> to master.  That's for the practical reason that, otherwise, almost
> every patch that goes to master would also go to branch-2.9.  With these
> rules, instead, patches that would only go to master will be deferred
> until after the branch.
>
> The other difference is qualitative: we want to get changes in those
> categories in as early as we can, so please don't delay until the end of
> the month if you can avoid it.
> ___
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] master now "frozen" for forking

[Stokes, Ian]

> Hello everyone.  We are at the point in the release cycle where
> traditionally we would fork a branch from master for release.  We have
> tried a slightly different approach a few times and I'd like to propose
> that we do it again.  Instead of forking immediately, I propose that we
> "freeze" master so that only bug fixes and previously posted feature
> enhancements go in, until approximately January 15, and then fork
> branch-2.9 from master.  Unless anyone has a serious objection, let's do
> this.

Hi Ben,

Am I right in think that cut off for feature enhancements previously discussed 
on the ML is now January 15th if the above proposal goes ahead?

I guess there was an assumption on the OVS DPDK side that we would branch on 
January 1st with bug fixes and previously discussed feature enhancements 
possible until end of January for the 2.9 release, official release of 2.9 then 
being February 15th?

Thanks
Ian
> 
> Thanks,
> 
> Ben.
> ___
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] master now "frozen" for forking

[Ben Pfaff]

Hello everyone.  We are at the point in the release cycle where
traditionally we would fork a branch from master for release.  We have
tried a slightly different approach a few times and I'd like to propose
that we do it again.  Instead of forking immediately, I propose that we
"freeze" master so that only bug fixes and previously posted feature
enhancements go in, until approximately January 15, and then fork
branch-2.9 from master.  Unless anyone has a serious objection, let's do
this.

Thanks,

Ben.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev