9:54 a.m.
On 2/1/19 8:25 AM, Kaleb Keithley wrote:
>
>
> On Fri, Feb 1, 2019 at 2:07 PM Matt Benjamin <mbenjami(a)redhat.com
> <mailto:mbenjami@redhat.com>> wrote:
>
> Defer to Frank and Kaleb on this.
>
> Frank and Kaleb?
>
> Matt
>
> On Wed, Jan 30, 2019 at 11:48 AM Daniel Gryniewicz <dang(a)redhat.com
> <mailto:dang@redhat.com>> wrote:
> >
> > I'm not sure about that one. It's a complicated backport, due to
all
> > the changes in the compound code related to async. What do people
> > think?
>
>
> If Dan thinks it's complex....
>
> We want to rebase our downstream to 2.7.x. While normally I like to be
> aggressive, I think in this case I'd like to split the difference and
> _not_ take the complex patch and rebase to 2.7.2 with confidence that
> it's reasonably solid.
>
> Then if you want we can take the complex patch into 2.7.3 in another
> month or two and let that soak upstream. Which would be good to get
> some miles on it as our next rebase after that will probably be to 2.8.x.
>
> My 2ยข
>
+1, this sounds like a good plan to me.
Works for me.
If someone wants to backport the patch in their downstream and test it, they can share the
backport upstream and we can then merge into 2.7.3 with confidence.
Frank