Thanks everyone for the feedback. Given that *TEZ-4577* is a regression in
*0.10.4*, I'm even more motivated to proceed with the *0.10.5* release,
which I’ll be starting in the next few days.
Stamatis*:* good point, the reason for creating branch-0.10.5 is that in
Tez, each release has its own dedicated release branch as part of the
standard *release process
<https://cwiki.apache.org/confluence/display/TEZ/Making+a+TEZ+Release>*.

Regards,
Laszlo Bodor


On Wed, 30 Apr 2025 at 09:50, Stamatis Zampetakis <zabe...@gmail.com> wrote:

> Looking forward to the new Tez release!
>
> I guess we don't really need a branch-0.10.5 since we are not gonna do
> a 0.10.5.X release but that's a minor point.
>
> Best,
> Stamatis
>
> On Tue, Apr 29, 2025 at 8:56 AM Ayush Saxena <ayush...@gmail.com> wrote:
> >
> > +1,
> > Sounds like a plan :-)
> >
> > -Ayush
> >
> > On Mon, 28 Apr 2025 at 19:22, László Bodor <bodorlaszlo0...@gmail.com>
> wrote:
> > >
> > > Hi All!
> > >
> > > Please refer to the previous thread before reading this one:
> > > https://lists.apache.org/thread/3txszr61tol7s8mk393j6ro9ghx3znbn
> > >
> > > The main question is whether we’re aware of any *bugs that could block
> a
> > > 0.10.5 release*. If not, the current master appears to be in good
> shape for
> > > that release.
> > >
> > > This release could also serve as a *milestone* for creating two new
> > > branches:
> > >
> > >    -
> > >
> > >    branch-0.10.5: for the 0.10.5 release specifically
> > >    -
> > >
> > >    branch-0.10: as the future *maintenance branch* for the 0.10.x line
> > >
> > > Following this, the versioning would move forward as:
> > >
> > >    -
> > >
> > >    master → 1.0.0-SNAPSHOT
> > >    -
> > >
> > >    branch-0.10 → 0.10.6-SNAPSHOT
> > >
> > >
> > > Regards,
> > > Laszlo Bodor
>

Reply via email to