We have had the last 2.x release. I don't think we did c-pick our security issues into the last release either. Will start the EOL vote for the 2.x release line as we discussed earlier
-Ayush On Sun, 21 Apr 2024 at 01:33, Chao Sun <sunc...@apache.org> wrote: > > Hi Cheng, > > Sorry for the long delay. I was distracted by other things. > > I just created RC0 for the Hive 2.3.10 release, and started a vote thread. > Please help to test if it looks good, especially from Spark side. Thanks! > > Best, > Chao > > > > On Thu, Apr 18, 2024 at 5:15 AM Cheng Pan <pan3...@gmail.com> wrote: >> >> Hi Chao, >> >> The Spark community is starting to discuss the 4.0 release[1], can we make >> the Hive 2.3.10 release happen soon? >> >> [1] https://lists.apache.org/thread/nxmvz2j7kp96otzlnl3kd277knlb6qgb >> >> Thanks, >> Cheng Pan >> >> On 2024/01/17 17:50:37 Chao Sun wrote: >> > Hi Ayush, >> > >> > I'm working on the last few commits to backport to the branch. >> > Hopefully within 1-2 months I can start the release process. Our goal >> > is to upgrade Hive 2.x before the Spark 4.0 release coming up mid this >> > year. >> > >> > Chao >> > >> > On Tue, Jan 16, 2024 at 10:17 PM Ayush Saxena <ay...@gmail.com> wrote: >> > > >> > > Thanx everyone for the feedback, I have started a formal thread to mark >> > > 1.x >> > > EOL. We can have one last release for 2.x as Chao mentioned, with some >> > > required changes + our CVE's & get the release line marked as EOL then. >> > > >> > > @Chao Sun <su...@apache.org> Do let us know if you have a proposed >> > > timeline for that. >> > > >> > > -Ayush >> > > >> > > On Wed, 17 Jan 2024 at 08:23, vihang karajgaonkar <vi...@apache.org> >> > > wrote: >> > > >> > > > I was confused about the subject line since it says 3.x as well along >> > > > with >> > > > 1.x and 2.x. Does this discussion include all 1.x, 2.x and 3.x or just >> > > > 1.x >> > > > and 2.x? >> > > > >> > > > I think it makes sense to EOL 1.x. Looks like 2.x is still being >> > > > maintained >> > > > by Chao and I think we were backporting PRs to the 3.x line pretty >> > > > recently >> > > > so I believe we should wait out for a release on Hive 3.x. >> > > > >> > > > Thanks, >> > > > Vihang >> > > > >> > > > On Tue, Jan 16, 2024 at 3:40 PM Attila Turoczy >> > > > <at...@cloudera.com.invalid> wrote: >> > > > >> > > > > Dear PMC's, >> > > > > >> > > > > Do we have a verdict / decision about this? >> > > > > >> > > > > -Attila >> > > > > >> > > > > On Wed, Jan 10, 2024 at 5:45 PM Chao Sun <su...@apache.org> wrote: >> > > > > >> > > > > > On Hive 2.x, I'm still preparing for another release 2.3.10 (Hive >> > > > > > 2.3 >> > > > > > branch is being actively maintained so far). Hopefully this will be >> > > > > > the last release in the branch-2 line. >> > > > > > >> > > > > > +1 on making Hive 1 EOL for the time being. >> > > > > > >> > > > > > Chao >> > > > > > >> > > > > > On Wed, Jan 10, 2024 at 8:10 AM Sankar Hariappan >> > > > > > <sa...@microsoft.com.invalid> wrote: >> > > > > > > >> > > > > > > +1 for making both Hive 1&2 EOL >> > > > > > > >> > > > > > > -Sankar >> > > > > > > -----Original Message----- >> > > > > > > From: Attila Turoczy <at...@cloudera.com.INVALID> >> > > > > > > Sent: Wednesday, January 10, 2024 7:37 PM >> > > > > > > To: dev@hive.apache.org >> > > > > > > Subject: [EXTERNAL] Re: [DISCUSS] End of life for Hive 1.x, 2.x, >> > > > > > > 3.x >> > > > > > > >> > > > > > > [You don't often get email from aturo...@cloudera.com.invalid. >> > > > > > > Learn >> > > > > > why this is important at >> > > > > > https://aka.ms/LearnAboutSenderIdentification >> > > > ] >> > > > > > > >> > > > > > > +1 for making it EOL for Hive 1 and Hive 2. I do not think these >> > > > > > > 2 >> > > > > > product >> > > > > > > branches are relevant in 2023. >> > > > > > > >> > > > > > > -Attila >> > > > > > > >> > > > > > > On Wed, Jan 10, 2024 at 12:59 PM Denys Kuzmenko < >> > > > dkuzme...@apache.org> >> > > > > > > wrote: >> > > > > > > >> > > > > > > > +1 for marking Hive 1.x EOL >> > > > > > > > >> > > > > > > > Assuming no volunteers willing to take ownership of branch-2 >> > > > > > maintenance, >> > > > > > > > +1 to declare it EOL as well. >> > > > > > > > >> > > > > > > > Regards, >> > > > > > > > Denys >> > > > > > > > >> > > > > > >> > > > > >> > > > >> > >> >> >>
