+1
On Fri, Dec 9, 2022 at 2:34 PM Sivabalan wrote:
> sure, sounds good to me. We have been dragging this for 2 weeks ish. So,
> let's go ahead w/ Dec 12.
>
> On Thu, 8 Dec 2022 at 22:33, Satish Kotha wrote:
>
> > Hi folks,
> >
> > Can we do Monday December 12 as code freeze date? Please chime
makes sense. sounds good to me!
On Fri, 9 Dec 2022 at 09:01, Y Ethan Guo wrote:
> Hi folks,
>
> As mentioned in another thread, RFC-46 (Optimize record payload handling)
> feature branch is planned for merging by the end of this week. Given that
> RFC-46 is a major enhancement for 0.13.0
Hi folks,
As mentioned in another thread, RFC-46 (Optimize record payload handling)
feature branch is planned for merging by the end of this week. Given that
RFC-46 is a major enhancement for 0.13.0 release, which requires more time
to solidify on master, it is better to give at least 4-week
+1
On Fri, Dec 9, 2022 at 10:23 PM Y Ethan Guo wrote:
> +1 on Dec 12 as the code freeze date
>
> On Fri, Dec 9, 2022 at 3:16 AM Shiyan Xu
> wrote:
>
> > +1
> >
> > On Fri, Dec 9, 2022 at 2:34 PM Sivabalan wrote:
> >
> > > sure, sounds good to me. We have been dragging this for 2 weeks ish.
>
+1
On Fri, Dec 9, 2022 at 11:09 PM Sivabalan wrote:
> makes sense. sounds good to me!
>
>
> On Fri, 9 Dec 2022 at 09:01, Y Ethan Guo wrote:
>
> > Hi folks,
> >
> > As mentioned in another thread, RFC-46 (Optimize record payload handling)
> > feature branch is planned for merging by the end of
Sounds good.
On 2022/11/09 21:23:15 Y Ethan Guo wrote:
> Hi folks,
>
> As the RM for the upcoming 0.13.0 release, I'd like to propose the
> following timeline based on the current progress of major features on our
> community roadmap:
>
> - *Dec 12, Monday, 11:59 PM PST*: 0.13.0 code freeze
> -
I agree that we can merge RFC-46 feature branch to master at the end of
this week to give leeway to 0.12.2.
On Tue, Dec 6, 2022 at 4:03 PM Alexey Kudinkin wrote:
> Thanks for bubbling this up, Siva!
>
> Merge has not happened yet.
>
> What you're saying makes sense to me -- after merging
+1 on Dec 12 as the code freeze date
On Fri, Dec 9, 2022 at 3:16 AM Shiyan Xu
wrote:
> +1
>
> On Fri, Dec 9, 2022 at 2:34 PM Sivabalan wrote:
>
> > sure, sounds good to me. We have been dragging this for 2 weeks ish. So,
> > let's go ahead w/ Dec 12.
> >
> > On Thu, 8 Dec 2022 at 22:33, Satish
Hi Shawy and RFC-46 group,
Thanks for bringing this up. Based on Alexey's latest update in another
thread, the RFC-46 feature branch is going to be merged soon. It makes
sense to me to let the new code fully baked in for 4 weeks and push back
the code freeze date of 0.13.0 to early Jan. I'll
