Hi Tanuj,

Do you have any expected timelines for this release? Happy to help and
support if anything required.


Thanks,
Rajeshbabu.

On Mon, Oct 3, 2022, 12:45 PM Istvan Toth <[email protected]> wrote:

> That would be great, Tanuj.
>
> If you have the cycles, you could also check for any missing easily
> backportable fixes from 5.1 compared to master, I'm sure that there are a
> few.
> I last synced the fixes from master about a year ago, when we were planning
> to release 5.1.3, but the release didn't happen then.
> (But even if you don't, releasing from the current 5.1 branch is still
> worthwhile)
>
> Also note that we haven't updated the release instructions yet with Viraj's
> scripts in *dev/misc_utils* that help to get the JIRA and release notes
> up-to-date.
>
> regards
> Istvan
>
> On Sat, Oct 1, 2022 at 8:43 PM Tanuj Khurana <[email protected]>
> wrote:
>
> > Hi Phoenix dev team,
> >
> > I am willing to volunteer as RM for Phoenix 5.1.3 release. There are a
> good
> > amount of fixes available in 5.1.3 worthy of a bugfix release. Let me
> know
> > if someone has any concerns.
> >
> > Regards,
> > Tanuj
> >
> > On Tue, 23 Aug 2022 at 09:09, Battula, Brahma Reddy
> > <[email protected]> wrote:
> >
> > > Looks there are good amount[1] of bugs are fixed in 5.1.3. Hence asked.
> > >
> > >
> > >
> > > 1.
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20fixVersion%20%3D%205.1.3
> > >
> > >
> > >
> > > On 23/08/22, 9:33 PM, "Istvan Toth" <[email protected]> wrote:
> > >
> > >     There is currently no 5.1.3 planned, the next release will be
> 5.2.0.
> > >
> > >     The 5.1 branch is quite stable, you may consider using 5.1 HEAD.
> > >
> > >     regards
> > >     Istvan
> > >
> > >     On Tue, Aug 23, 2022 at 4:01 PM Battula, Brahma Reddy
> > >     <[email protected]> wrote:
> > >
> > >     > Hi All,
> > >     >
> > >     > May I know the release plan for 5.1.3..?
> > >     >
> > >     >
> > >     > Regards
> > >     > Brahma Reddy Battula
> > >     >
> > >
> > >
> >
>

Reply via email to