On Mon, Jul 09, 2018 at 10:48:51AM +0530, Numan Siddique wrote:
> On Thu, Jul 5, 2018 at 11:46 PM Han Zhou wrote:
>
> > On Mon, Jul 2, 2018 at 9:48 AM, Ben Pfaff wrote:
> > >
> > > According to our release process, we should fork branch-2.10 from master
> > > July 1 (yesterday), then release on
On Thu, Jul 5, 2018 at 11:46 PM Han Zhou wrote:
> On Mon, Jul 2, 2018 at 9:48 AM, Ben Pfaff wrote:
> >
> > According to our release process, we should fork branch-2.10 from master
> > July 1 (yesterday), then release on August 15. I'm going to propose
> > that we modify this in the same way
On Thu, Jul 05, 2018 at 11:16:08AM -0700, Han Zhou wrote:
> Here are some patches related to bug fixes I have in mind that should be in
> 2.10.
>
> Fixing port-group:
> https://patchwork.ozlabs.org/patch/931913/
>
> and the follow up patch of above one:
>
On Mon, Jul 2, 2018 at 9:48 AM, Ben Pfaff wrote:
>
> According to our release process, we should fork branch-2.10 from master
> July 1 (yesterday), then release on August 15. I'm going to propose
> that we modify this in the same way that has been successful in the
> past, by calling for an
According to our release process, we should fork branch-2.10 from master
July 1 (yesterday), then release on August 15. I'm going to propose
that we modify this in the same way that has been successful in the
past, by calling for an approximately 2-week "soft freeze". During the
freeze period,
