Re: 0.13.0 release timeline

[Y Ethan Guo]

Hi folks,

I've already cut the branch
 for 0.13.0 RC1.  I'm
preparing the artifacts and deploying them to the staging area.  Once done,
I'll put up a voting thread.

Thanks,
- Ethan

On Mon, Jan 9, 2023 at 10:24 PM Y Ethan Guo  wrote:

> Hi folks,
>
> Given that there are still a few release blockers
> 
> to address, as the RM, I propose to postpone the code freeze of the 0.13.0
> release to *Jan 23, Tuesday, 11:59 PM PST*.  We should also aim for the
> testing of the new features to be done by then.
>
> Thanks,
> - Ethan
>
> On Mon, Dec 12, 2022 at 9:53 AM Y Ethan Guo  wrote:
>
>> Thank you folks for chiming in.
>>
>> The new code freeze date of the 0.13.0 release is *Jan 10, Tuesday, 11:59
>> PM PST*.
>>
>> Thanks,
>> - Ethan
>>
>> On Fri, Dec 9, 2022 at 9:42 AM sagar sumit  wrote:
>>
>>> +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 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 baked-in
>>> > time.
>>> > >
>>> > > As the RM, I propose that we push back the code freeze date of the
>>> 0.13.0
>>> > > release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your
>>> thoughts
>>> > with
>>> > > yes/no.
>>> > >
>>> > > Thanks,
>>> > > - Ethan
>>> > >
>>> >
>>> >
>>> > --
>>> > Regards,
>>> > -Sivabalan
>>> >
>>>
>>

Re: 0.13.0 release timeline

[Y Ethan Guo]

Hi folks,

Given that there are still a few release blockers

to address, as the RM, I propose to postpone the code freeze of the 0.13.0
release to *Jan 23, Tuesday, 11:59 PM PST*.  We should also aim for the
testing of the new features to be done by then.

Thanks,
- Ethan

On Mon, Dec 12, 2022 at 9:53 AM Y Ethan Guo  wrote:

> Thank you folks for chiming in.
>
> The new code freeze date of the 0.13.0 release is *Jan 10, Tuesday, 11:59
> PM PST*.
>
> Thanks,
> - Ethan
>
> On Fri, Dec 9, 2022 at 9:42 AM sagar sumit  wrote:
>
>> +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 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 baked-in
>> > time.
>> > >
>> > > As the RM, I propose that we push back the code freeze date of the
>> 0.13.0
>> > > release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your thoughts
>> > with
>> > > yes/no.
>> > >
>> > > Thanks,
>> > > - Ethan
>> > >
>> >
>> >
>> > --
>> > Regards,
>> > -Sivabalan
>> >
>>
>

Re: 0.13.0 release timeline

[Y Ethan Guo]

Thank you folks for chiming in.

The new code freeze date of the 0.13.0 release is *Jan 10, Tuesday, 11:59
PM PST*.

Thanks,
- Ethan

On Fri, Dec 9, 2022 at 9:42 AM sagar sumit  wrote:

> +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 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 baked-in
> > time.
> > >
> > > As the RM, I propose that we push back the code freeze date of the
> 0.13.0
> > > release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your thoughts
> > with
> > > yes/no.
> > >
> > > Thanks,
> > > - Ethan
> > >
> >
> >
> > --
> > Regards,
> > -Sivabalan
> >
>

RE: 0.13.0 release timeline

[Frank Wong]

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
> - *Dec 13/14, PST*: Cut release branch and start RC1 voting
>
> All the major features should be landed at least a couple of days before
> the code freeze date so that there is time to land more fixes if needed.
>
> Please raise any concerns if you have one by the end of this week.
>
> If you have not done already, please tag any JIRAs that you have planned
> for the 0.13.0 release by setting the "Fix Version/s" to "0.13.0" and mark
> PRs to be landed for 0.13.0 with the label "priority:blocker".
>
> Thanks,
> - Ethan
>

Re: 0.13.0 release timeline

[sagar sumit]

+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 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 baked-in
> time.
> >
> > As the RM, I propose that we push back the code freeze date of the 0.13.0
> > release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your thoughts
> with
> > yes/no.
> >
> > Thanks,
> > - Ethan
> >
>
>
> --
> Regards,
> -Sivabalan
>

Re: 0.13.0 release timeline

[Sivabalan]

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 release, which requires more time
> to solidify on master, it is better to give at least 4-week baked-in time.
>
> As the RM, I propose that we push back the code freeze date of the 0.13.0
> release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your thoughts with
> yes/no.
>
> Thanks,
> - Ethan
>


-- 
Regards,
-Sivabalan

Re: 0.13.0 release timeline

[Y Ethan Guo]

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 baked-in time.

As the RM, I propose that we push back the code freeze date of the 0.13.0
release to *Jan 10, Tuesday, 11:59 PM PST*.  Let me know your thoughts with
yes/no.

Thanks,
- Ethan

0.13.0 release timeline

[Y Ethan Guo]

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
- *Dec 13/14, PST*: Cut release branch and start RC1 voting

All the major features should be landed at least a couple of days before
the code freeze date so that there is time to land more fixes if needed.

Please raise any concerns if you have one by the end of this week.

If you have not done already, please tag any JIRAs that you have planned
for the 0.13.0 release by setting the "Fix Version/s" to "0.13.0" and mark
PRs to be landed for 0.13.0 with the label "priority:blocker".

Thanks,
- Ethan