I think this is a great initiative. Not only are you giving a reminder about
the need to implement new features in a modular and pluggable way, but you are
also providing a real example with an already implemented not in the best way
feature, to show the steps to follow in the right direction fo
I know we have folks spread across different time zones, would a 9AM PST / 4PM
UTC discussion work? Yes, we will post the recording afterwards but that makes
it hard to ask live questions :-)
Anthony
> On Sep 21, 2021, at 12:14 AM, Alberto Gomez wrote:
>
> I think this is a great initiative
Shoot I have a personal appointment that day I can’t move at that time. We
could schedule a special session for this or move the community meeting to a
different day. I could do Monday or Tuesday that week at 9:00 am PDT.
> On Sep 21, 2021, at 8:14 AM, Anthony Baker wrote:
>
> I know we have
Devs,
In addition to my discussion regarding the modularization of the WAN TX
batching implementation I would like to propose that we remove the
serialization changes that went into 1.14 to support it. Since the feature is
not complete in 1.14 this should only impact the associated tests in 1.1
+1.
Is the idea just creating the Jira tickets? It is not clear from here, if it
will be owned and completed by 1.15.
-Anil.
On 9/21/21, 2:13 PM, "Jacob Barrett" wrote:
Devs,
In addition to my discussion regarding the modularization of the WAN TX
batching implementation I would lik
> On Sep 21, 2021, at 2:32 PM, Anilkumar Gingade wrote:
> Is the idea just creating the Jira tickets? It is not clear from here, if it
> will be owned and completed by 1.15.
I will create two tickets:
1) To address 1.14 and anyone can pick this up, but if nobody does I will.
2) To block 1.15
