Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2024-01-24 Thread Battula, Brahma Reddy
Hi Stamatis,

Any further update on the following which we missed here. thanks


Regards,
Brahma.


From: Stamatis Zampetakis 
Date: Tuesday, August 1, 2023 at 17:05
To: dev@hive.apache.org 
Subject: Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal
Hello,

HIVE-27504 is now merged to master. Thanks everyone for the reviews!

I am going to prepare the release candidate for 4.0.0-beta-1 sometime this week.

Best,
Stamatis

On Thu, Jul 27, 2023 at 1:54 PM Battula, Brahma Reddy
 wrote:
>
> Looks following PR is reviewed. Any chance to get it merged and give the 
> release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis"  <mailto:zabe...@gmail.com>> wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30/07. If HIVE-27504 does not land in the next day or two the beta-1
> release might get delayed unless someone else picks up the RM role and
> cuts the RC.
>
>
> Best,
> Stamatis
>
>
> On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
>  <mailto:aturo...@cloudera.com.inva>lid<mailto:aturo...@cloudera.com.inva%3elid>>
>  wrote:
> >
> > Thanks for the update! Can't wait for the beta :)
> >
> > -Attila
> >
> > On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis  > <mailto:zabe...@gmail.com>>
> > wrote:
> >
> > > Hey everyone,
> > >
> > > As you may have noticed there have been various tickets around LICENSE
> > > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > > which hopefully addresses all remaining issues that were found while I
> > > was working with the RC. After this gets resolved we should be good to
> > > go for putting up the RC for vote.
> > >
> > > The structure and content of the LICENSE and NOTICE file are very
> > > important for Apache releases so I would encourage other members of
> > > the community (especially PMC) to review the latest changes and
> > > current status and raise new JIRA tickets if they discover some
> > > problems. I would like to avoid having last minute -1 votes due to
> > > that.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] 
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D=0<https://issues.apache.org/jira/browse/HIVE-27504>
> > >  
> > > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FHIVE-27504=05%7C01%7Cbbattula%40visa.com%7C79a71df0f45047b2388708db92836740%7C38305e12e15d4ee888b9c4db1c477d76%7C0%7C0%7C638264865295588150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=jYi7uYaZRu7DeTziITt3tsrJsq605SYZdrVzC594580%3D=0<https://issues.apache.org/jira/browse/HIVE-27504>>
> > >
> > > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  > > <mailto:zabe...@gmail.com>>
> > > wrote:
> > > >
> > > > Hey team,
> > > >
> > > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > > >
> > > > Most of the release steps went out smoothly and I was able to get an
> > > > RC0 ready [1].
> > > >
> > > > However, I am afraid that our binary distribution does not comply
> > > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > > within and I am not sure if we are fully covered in terms of licenses
> > > > and notice files. Thanks Ayush for reminding me to check the
> > > > binary-package-licenses directory [5].
> > > >
> > > > I am checking various resources such as [3, 4] to see what additional
> > > > steps we can take to be on the safe side and also looking for ways to
> > > > automate this so that we don't have to manually inspect the jars on
> > > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > > am not yet completely happy with its output.
> > > >
> > > > The next few days will be a bit busy so most likely I will get back on
> > > > this during the weekend. If people have feedback or other ideas to
> > > > share please let me know.
> > > >
> >

Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-08-01 Thread Stamatis Zampetakis
Hello,

HIVE-27504 is now merged to master. Thanks everyone for the reviews!

I am going to prepare the release candidate for 4.0.0-beta-1 sometime this week.

Best,
Stamatis

On Thu, Jul 27, 2023 at 1:54 PM Battula, Brahma Reddy
 wrote:
>
> Looks following PR is reviewed. Any chance to get it merged and give the 
> release.?
>
> On 18/07/23, 2:39 PM, "Stamatis Zampetakis"  > wrote:
>
>
> HIVE-27504 still lacks reviews from committers.
>
>
> Note that I will not be able to work on the release from 22/07 to
> 30/07. If HIVE-27504 does not land in the next day or two the beta-1
> release might get delayed unless someone else picks up the RM role and
> cuts the RC.
>
>
> Best,
> Stamatis
>
>
> On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
> mailto:aturo...@cloudera.com.inva>lid> wrote:
> >
> > Thanks for the update! Can't wait for the beta :)
> >
> > -Attila
> >
> > On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis  > >
> > wrote:
> >
> > > Hey everyone,
> > >
> > > As you may have noticed there have been various tickets around LICENSE
> > > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > > which hopefully addresses all remaining issues that were found while I
> > > was working with the RC. After this gets resolved we should be good to
> > > go for putting up the RC for vote.
> > >
> > > The structure and content of the LICENSE and NOTICE file are very
> > > important for Apache releases so I would encourage other members of
> > > the community (especially PMC) to review the latest changes and
> > > current status and raise new JIRA tickets if they discover some
> > > problems. I would like to avoid having last minute -1 votes due to
> > > that.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://issues.apache.org/jira/browse/HIVE-27504 
> > > 
> > >
> > > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  > > >
> > > wrote:
> > > >
> > > > Hey team,
> > > >
> > > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > > >
> > > > Most of the release steps went out smoothly and I was able to get an
> > > > RC0 ready [1].
> > > >
> > > > However, I am afraid that our binary distribution does not comply
> > > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > > within and I am not sure if we are fully covered in terms of licenses
> > > > and notice files. Thanks Ayush for reminding me to check the
> > > > binary-package-licenses directory [5].
> > > >
> > > > I am checking various resources such as [3, 4] to see what additional
> > > > steps we can take to be on the safe side and also looking for ways to
> > > > automate this so that we don't have to manually inspect the jars on
> > > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > > am not yet completely happy with its output.
> > > >
> > > > The next few days will be a bit busy so most likely I will get back on
> > > > this during the weekend. If people have feedback or other ideas to
> > > > share please let me know.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/ 
> > > > 
> > > > [2]
> > > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> > >  
> > > 
> > > > [3] https://infra.apache.org/licensing-howto.html 
> > > > 
> > > > [4] https://www.apache.org/legal/resolved.html 
> > > > 
> > > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses 
> > > > 
> > > > [6] https://www.mojohaus.org/license-maven-plugin/ 
> > > > 
> > > >
> > > >
> > > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis  > > > >
> > > wrote:
> > > > >
> > > > > I can start preparing the RC towards the end of next week. If somebody
> > > > > has more time and wants to start earlier I am fine to switch.
> > > > >
> > > > > Best,
> > > > > Stamatis
> > > > >
> > > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  > > > > >
> > > wrote:
> > > > > >
> > > > > > great, this is the current list of release managers:
> > > > > >
> > > > > > 4.0.0 Stamatis Zampetakis
> > > > > > 4.1.0 Denys Kuzmenko
> > > > > > 4.2.0 Sai Hemanth Gantasala
> > > > > >
> > > > > > Should we keep the same RM order and just shift the releases or find
> > > a volunteer for the 4.0.0-beta release, WDYT?
> > > > > >
> > > > > >
> > >
>
>
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-07-27 Thread Battula, Brahma Reddy
Looks following PR is reviewed. Any chance to get it merged and give the 
release.?

On 18/07/23, 2:39 PM, "Stamatis Zampetakis" mailto:zabe...@gmail.com>> wrote:


HIVE-27504 still lacks reviews from committers.


Note that I will not be able to work on the release from 22/07 to
30/07. If HIVE-27504 does not land in the next day or two the beta-1
release might get delayed unless someone else picks up the RM role and
cuts the RC.


Best,
Stamatis


On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
mailto:aturo...@cloudera.com.inva>lid> wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis  >
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various tickets around LICENSE
> > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > which hopefully addresses all remaining issues that were found while I
> > was working with the RC. After this gets resolved we should be good to
> > go for putting up the RC for vote.
> >
> > The structure and content of the LICENSE and NOTICE file are very
> > important for Apache releases so I would encourage other members of
> > the community (especially PMC) to review the latest changes and
> > current status and raise new JIRA tickets if they discover some
> > problems. I would like to avoid having last minute -1 votes due to
> > that.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-27504 
> > 
> >
> > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  > >
> > wrote:
> > >
> > > Hey team,
> > >
> > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > >
> > > Most of the release steps went out smoothly and I was able to get an
> > > RC0 ready [1].
> > >
> > > However, I am afraid that our binary distribution does not comply
> > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > within and I am not sure if we are fully covered in terms of licenses
> > > and notice files. Thanks Ayush for reminding me to check the
> > > binary-package-licenses directory [5].
> > >
> > > I am checking various resources such as [3, 4] to see what additional
> > > steps we can take to be on the safe side and also looking for ways to
> > > automate this so that we don't have to manually inspect the jars on
> > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > am not yet completely happy with its output.
> > >
> > > The next few days will be a bit busy so most likely I will get back on
> > > this during the weekend. If people have feedback or other ideas to
> > > share please let me know.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/ 
> > > 
> > > [2]
> > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> >  
> > 
> > > [3] https://infra.apache.org/licensing-howto.html 
> > > 
> > > [4] https://www.apache.org/legal/resolved.html 
> > > 
> > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses 
> > > 
> > > [6] https://www.mojohaus.org/license-maven-plugin/ 
> > > 
> > >
> > >
> > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis  > > >
> > wrote:
> > > >
> > > > I can start preparing the RC towards the end of next week. If somebody
> > > > has more time and wants to start earlier I am fine to switch.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  > > > >
> > wrote:
> > > > >
> > > > > great, this is the current list of release managers:
> > > > >
> > > > > 4.0.0 Stamatis Zampetakis
> > > > > 4.1.0 Denys Kuzmenko
> > > > > 4.2.0 Sai Hemanth Gantasala
> > > > >
> > > > > Should we keep the same RM order and just shift the releases or find
> > a volunteer for the 4.0.0-beta release, WDYT?
> > > > >
> > > > >
> >





Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-07-18 Thread Stamatis Zampetakis
HIVE-27504 still lacks reviews from committers.

Note that I will not be able to work on the release from 22/07 to
30/07. If HIVE-27504 does not land in the next day or two the beta-1
release might get delayed unless someone else picks up the RM role and
cuts the RC.

Best,
Stamatis

On Thu, Jul 13, 2023 at 6:33 PM Attila Turoczy
 wrote:
>
> Thanks for the update! Can't wait for the beta :)
>
> -Attila
>
> On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis 
> wrote:
>
> > Hey everyone,
> >
> > As you may have noticed there have been various tickets around LICENSE
> > and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> > which hopefully addresses all remaining issues that were found while I
> > was working with the RC. After this gets resolved we should be good to
> > go for putting up the RC for vote.
> >
> > The structure and content of the LICENSE and NOTICE file are very
> > important for Apache releases so I would encourage other members of
> > the community (especially PMC) to review the latest changes and
> > current status and raise new JIRA tickets if they discover some
> > problems. I would like to avoid having last minute -1 votes due to
> > that.
> >
> > Best,
> > Stamatis
> >
> > [1] https://issues.apache.org/jira/browse/HIVE-27504
> >
> > On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis 
> > wrote:
> > >
> > > Hey team,
> > >
> > > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> > >
> > > Most of the release steps went out smoothly and I was able to get an
> > > RC0 ready [1].
> > >
> > > However, I am afraid that our binary distribution does not comply
> > > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > > within and I am not sure if we are fully covered in terms of licenses
> > > and notice files. Thanks Ayush for reminding me to check the
> > > binary-package-licenses directory [5].
> > >
> > > I am checking various resources such as [3, 4] to see what additional
> > > steps we can take to be on the safe side and also looking for ways to
> > > automate this so that we don't have to manually inspect the jars on
> > > every release. I was playing a bit with license-maven-plugin [6] but I
> > > am not yet completely happy with its output.
> > >
> > > The next few days will be a bit busy so most likely I will get back on
> > > this during the weekend. If people have feedback or other ideas to
> > > share please let me know.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> > > [2]
> > https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> > > [3] https://infra.apache.org/licensing-howto.html
> > > [4] https://www.apache.org/legal/resolved.html
> > > [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> > > [6] https://www.mojohaus.org/license-maven-plugin/
> > >
> > >
> > > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis 
> > wrote:
> > > >
> > > > I can start preparing the RC towards the end of next week. If somebody
> > > > has more time and wants to start earlier I am fine to switch.
> > > >
> > > > Best,
> > > > Stamatis
> > > >
> > > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko 
> > wrote:
> > > > >
> > > > > great, this is the current list of release managers:
> > > > >
> > > > > 4.0.0 Stamatis Zampetakis
> > > > > 4.1.0 Denys Kuzmenko
> > > > > 4.2.0 Sai Hemanth Gantasala
> > > > >
> > > > > Should we keep the same RM order and just shift the releases or find
> > a volunteer for the 4.0.0-beta release, WDYT?
> > > > >
> > > > >
> >


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-07-13 Thread Attila Turoczy
Thanks for the update! Can't wait for the beta :)

-Attila

On Thu, Jul 13, 2023 at 5:19 PM Stamatis Zampetakis 
wrote:

> Hey everyone,
>
> As you may have noticed there have been various tickets around LICENSE
> and NOTICE files popping up recently. I just logged HIVE-27504 [1]
> which hopefully addresses all remaining issues that were found while I
> was working with the RC. After this gets resolved we should be good to
> go for putting up the RC for vote.
>
> The structure and content of the LICENSE and NOTICE file are very
> important for Apache releases so I would encourage other members of
> the community (especially PMC) to review the latest changes and
> current status and raise new JIRA tickets if they discover some
> problems. I would like to avoid having last minute -1 votes due to
> that.
>
> Best,
> Stamatis
>
> [1] https://issues.apache.org/jira/browse/HIVE-27504
>
> On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis 
> wrote:
> >
> > Hey team,
> >
> > Small heads up regarding the progress of the 4.0.0-beta-1 release.
> >
> > Most of the release steps went out smoothly and I was able to get an
> > RC0 ready [1].
> >
> > However, I am afraid that our binary distribution does not comply
> > fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> > within and I am not sure if we are fully covered in terms of licenses
> > and notice files. Thanks Ayush for reminding me to check the
> > binary-package-licenses directory [5].
> >
> > I am checking various resources such as [3, 4] to see what additional
> > steps we can take to be on the safe side and also looking for ways to
> > automate this so that we don't have to manually inspect the jars on
> > every release. I was playing a bit with license-maven-plugin [6] but I
> > am not yet completely happy with its output.
> >
> > The next few days will be a bit busy so most likely I will get back on
> > this during the weekend. If people have feedback or other ideas to
> > share please let me know.
> >
> > Best,
> > Stamatis
> >
> > [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> > [2]
> https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> > [3] https://infra.apache.org/licensing-howto.html
> > [4] https://www.apache.org/legal/resolved.html
> > [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> > [6] https://www.mojohaus.org/license-maven-plugin/
> >
> >
> > On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis 
> wrote:
> > >
> > > I can start preparing the RC towards the end of next week. If somebody
> > > has more time and wants to start earlier I am fine to switch.
> > >
> > > Best,
> > > Stamatis
> > >
> > > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko 
> wrote:
> > > >
> > > > great, this is the current list of release managers:
> > > >
> > > > 4.0.0 Stamatis Zampetakis
> > > > 4.1.0 Denys Kuzmenko
> > > > 4.2.0 Sai Hemanth Gantasala
> > > >
> > > > Should we keep the same RM order and just shift the releases or find
> a volunteer for the 4.0.0-beta release, WDYT?
> > > >
> > > >
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-07-13 Thread Stamatis Zampetakis
Hey everyone,

As you may have noticed there have been various tickets around LICENSE
and NOTICE files popping up recently. I just logged HIVE-27504 [1]
which hopefully addresses all remaining issues that were found while I
was working with the RC. After this gets resolved we should be good to
go for putting up the RC for vote.

The structure and content of the LICENSE and NOTICE file are very
important for Apache releases so I would encourage other members of
the community (especially PMC) to review the latest changes and
current status and raise new JIRA tickets if they discover some
problems. I would like to avoid having last minute -1 votes due to
that.

Best,
Stamatis

[1] https://issues.apache.org/jira/browse/HIVE-27504

On Tue, Jun 20, 2023 at 11:09 PM Stamatis Zampetakis  wrote:
>
> Hey team,
>
> Small heads up regarding the progress of the 4.0.0-beta-1 release.
>
> Most of the release steps went out smoothly and I was able to get an
> RC0 ready [1].
>
> However, I am afraid that our binary distribution does not comply
> fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
> within and I am not sure if we are fully covered in terms of licenses
> and notice files. Thanks Ayush for reminding me to check the
> binary-package-licenses directory [5].
>
> I am checking various resources such as [3, 4] to see what additional
> steps we can take to be on the safe side and also looking for ways to
> automate this so that we don't have to manually inspect the jars on
> every release. I was playing a bit with license-maven-plugin [6] but I
> am not yet completely happy with its output.
>
> The next few days will be a bit busy so most likely I will get back on
> this during the weekend. If people have feedback or other ideas to
> share please let me know.
>
> Best,
> Stamatis
>
> [1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
> [2] 
> https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
> [3] https://infra.apache.org/licensing-howto.html
> [4] https://www.apache.org/legal/resolved.html
> [5] https://github.com/apache/hive/tree/master/binary-package-licenses
> [6] https://www.mojohaus.org/license-maven-plugin/
>
>
> On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis  wrote:
> >
> > I can start preparing the RC towards the end of next week. If somebody
> > has more time and wants to start earlier I am fine to switch.
> >
> > Best,
> > Stamatis
> >
> > On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  wrote:
> > >
> > > great, this is the current list of release managers:
> > >
> > > 4.0.0 Stamatis Zampetakis
> > > 4.1.0 Denys Kuzmenko
> > > 4.2.0 Sai Hemanth Gantasala
> > >
> > > Should we keep the same RM order and just shift the releases or find a 
> > > volunteer for the 4.0.0-beta release, WDYT?
> > >
> > >


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-20 Thread Stamatis Zampetakis
Hey team,

Small heads up regarding the progress of the 4.0.0-beta-1 release.

Most of the release steps went out smoothly and I was able to get an
RC0 ready [1].

However, I am afraid that our binary distribution does not comply
fully with the ASF Policy [2]. We bundle a lot of dependencies (jars)
within and I am not sure if we are fully covered in terms of licenses
and notice files. Thanks Ayush for reminding me to check the
binary-package-licenses directory [5].

I am checking various resources such as [3, 4] to see what additional
steps we can take to be on the safe side and also looking for ways to
automate this so that we don't have to manually inspect the jars on
every release. I was playing a bit with license-maven-plugin [6] but I
am not yet completely happy with its output.

The next few days will be a bit busy so most likely I will get back on
this during the weekend. If people have feedback or other ideas to
share please let me know.

Best,
Stamatis

[1] https://people.apache.org/~zabetak/apache-hive-4.0.0-beta-1-rc0/
[2] 
https://www.apache.org/legal/src-headers.html#asf-source-header-and-copyright-notice-policy
[3] https://infra.apache.org/licensing-howto.html
[4] https://www.apache.org/legal/resolved.html
[5] https://github.com/apache/hive/tree/master/binary-package-licenses
[6] https://www.mojohaus.org/license-maven-plugin/


On Fri, Jun 2, 2023 at 10:03 PM Stamatis Zampetakis  wrote:
>
> I can start preparing the RC towards the end of next week. If somebody
> has more time and wants to start earlier I am fine to switch.
>
> Best,
> Stamatis
>
> On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  wrote:
> >
> > great, this is the current list of release managers:
> >
> > 4.0.0 Stamatis Zampetakis
> > 4.1.0 Denys Kuzmenko
> > 4.2.0 Sai Hemanth Gantasala
> >
> > Should we keep the same RM order and just shift the releases or find a 
> > volunteer for the 4.0.0-beta release, WDYT?
> >
> >


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-02 Thread Stamatis Zampetakis
I can start preparing the RC towards the end of next week. If somebody
has more time and wants to start earlier I am fine to switch.

Best,
Stamatis

On Fri, Jun 2, 2023 at 5:36 PM Denys Kuzmenko  wrote:
>
> great, this is the current list of release managers:
>
> 4.0.0 Stamatis Zampetakis
> 4.1.0 Denys Kuzmenko
> 4.2.0 Sai Hemanth Gantasala
>
> Should we keep the same RM order and just shift the releases or find a 
> volunteer for the 4.0.0-beta release, WDYT?
>
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-02 Thread Denys Kuzmenko
great, this is the current list of release managers:

4.0.0 Stamatis Zampetakis
4.1.0 Denys Kuzmenko
4.2.0 Sai Hemanth Gantasala

Should we keep the same RM order and just shift the releases or find a 
volunteer for the 4.0.0-beta release, WDYT? 




Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-02 Thread Ayush Saxena
+1, for a pre GA release

Beta sounds better to me, we don’t have any half baked major features, just
probabilities of some bugs

-Ayush

On Thu, 1 Jun 2023 at 4:24 PM, Attila Turoczy 
wrote:

> Ayush just told me, the mailing list does not support images. It is a very
> sad world :-(
>
> Previous meme:
> https://imgflip.com/i/7nuzql
>
> On Thu, Jun 1, 2023 at 11:46 AM Attila Turoczy 
> wrote:
>
>> OK. Then let's go with beta. Please start. (if not started already) a
>> vote for a release.
>>
>> I think we should have a more frequent release cadence. The community
>> needs it, we need this, also without frequent release nobody will believe
>> this project is healthy. I know the first will be the hardest, but we need
>> to fix those issues and release them. Even a monthly release could be
>> possible for hive. We are capable to do this!
>>
>> [image: image.png]
>>
>> -Attila
>>
>> On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis 
>> wrote:
>>
>>> +1 from me as well. Any alpha or beta name should be fine I have no
>>> strong preferences.
>>>
>>> On Wed, May 31, 2023, 2:30 PM László Bodor 
>>> wrote:
>>>
>>> > Hi!
>>> >
>>> > +1 for creating a new release before GA in the presence of possible
>>> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
>>> with
>>> > alpha-3.
>>> >
>>> > Regards,
>>> > Laszlo Bodor
>>> >
>>> > Denys Kuzmenko  ezt írta (időpont: 2023. máj.
>>> 31.,
>>> > Sze, 14:22):
>>> >
>>> > > Hi folks,
>>> > >
>>> > > The master branch has many new features, bug fixes, and performance
>>> > > improvements since alpha-2. However, we still have several
>>> correctness
>>> > bugs
>>> > > [HIVE-26654] and performance issues that should be eliminated before
>>> the
>>> > > GA.
>>> > >
>>> > > Could we consider doing a beta release to keep at least a 6-month
>>> release
>>> > > cadence and also show the community that 4.0.0 GA is the next stop?
>>> > >
>>> > > Thanks,
>>> > > Denys
>>> > >
>>> >
>>>
>>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Attila Turoczy
Ayush just told me, the mailing list does not support images. It is a very
sad world :-(

Previous meme:
https://imgflip.com/i/7nuzql

On Thu, Jun 1, 2023 at 11:46 AM Attila Turoczy 
wrote:

> OK. Then let's go with beta. Please start. (if not started already) a vote
> for a release.
>
> I think we should have a more frequent release cadence. The community
> needs it, we need this, also without frequent release nobody will believe
> this project is healthy. I know the first will be the hardest, but we need
> to fix those issues and release them. Even a monthly release could be
> possible for hive. We are capable to do this!
>
> [image: image.png]
>
> -Attila
>
> On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis 
> wrote:
>
>> +1 from me as well. Any alpha or beta name should be fine I have no
>> strong preferences.
>>
>> On Wed, May 31, 2023, 2:30 PM László Bodor 
>> wrote:
>>
>> > Hi!
>> >
>> > +1 for creating a new release before GA in the presence of possible
>> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
>> with
>> > alpha-3.
>> >
>> > Regards,
>> > Laszlo Bodor
>> >
>> > Denys Kuzmenko  ezt írta (időpont: 2023. máj.
>> 31.,
>> > Sze, 14:22):
>> >
>> > > Hi folks,
>> > >
>> > > The master branch has many new features, bug fixes, and performance
>> > > improvements since alpha-2. However, we still have several correctness
>> > bugs
>> > > [HIVE-26654] and performance issues that should be eliminated before
>> the
>> > > GA.
>> > >
>> > > Could we consider doing a beta release to keep at least a 6-month
>> release
>> > > cadence and also show the community that 4.0.0 GA is the next stop?
>> > >
>> > > Thanks,
>> > > Denys
>> > >
>> >
>>
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Attila Turoczy
OK. Then let's go with beta. Please start. (if not started already) a vote
for a release.

I think we should have a more frequent release cadence. The community needs
it, we need this, also without frequent release nobody will believe this
project is healthy. I know the first will be the hardest, but we need to
fix those issues and release them. Even a monthly release could be possible
for hive. We are capable to do this!

[image: image.png]

-Attila

On Thu, Jun 1, 2023 at 11:24 AM Stamatis Zampetakis 
wrote:

> +1 from me as well. Any alpha or beta name should be fine I have no
> strong preferences.
>
> On Wed, May 31, 2023, 2:30 PM László Bodor 
> wrote:
>
> > Hi!
> >
> > +1 for creating a new release before GA in the presence of possible
> > correctness problems. I'm not 100% sure about alpha or beta, I'm fine
> with
> > alpha-3.
> >
> > Regards,
> > Laszlo Bodor
> >
> > Denys Kuzmenko  ezt írta (időpont: 2023. máj. 31.,
> > Sze, 14:22):
> >
> > > Hi folks,
> > >
> > > The master branch has many new features, bug fixes, and performance
> > > improvements since alpha-2. However, we still have several correctness
> > bugs
> > > [HIVE-26654] and performance issues that should be eliminated before
> the
> > > GA.
> > >
> > > Could we consider doing a beta release to keep at least a 6-month
> release
> > > cadence and also show the community that 4.0.0 GA is the next stop?
> > >
> > > Thanks,
> > > Denys
> > >
> >
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-06-01 Thread Stamatis Zampetakis
+1 from me as well. Any alpha or beta name should be fine I have no
strong preferences.

On Wed, May 31, 2023, 2:30 PM László Bodor 
wrote:

> Hi!
>
> +1 for creating a new release before GA in the presence of possible
> correctness problems. I'm not 100% sure about alpha or beta, I'm fine with
> alpha-3.
>
> Regards,
> Laszlo Bodor
>
> Denys Kuzmenko  ezt írta (időpont: 2023. máj. 31.,
> Sze, 14:22):
>
> > Hi folks,
> >
> > The master branch has many new features, bug fixes, and performance
> > improvements since alpha-2. However, we still have several correctness
> bugs
> > [HIVE-26654] and performance issues that should be eliminated before the
> > GA.
> >
> > Could we consider doing a beta release to keep at least a 6-month release
> > cadence and also show the community that 4.0.0 GA is the next stop?
> >
> > Thanks,
> > Denys
> >
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-05-31 Thread László Bodor
Hi!

+1 for creating a new release before GA in the presence of possible
correctness problems. I'm not 100% sure about alpha or beta, I'm fine with
alpha-3.

Regards,
Laszlo Bodor

Denys Kuzmenko  ezt írta (időpont: 2023. máj. 31.,
Sze, 14:22):

> Hi folks,
>
> The master branch has many new features, bug fixes, and performance
> improvements since alpha-2. However, we still have several correctness bugs
> [HIVE-26654] and performance issues that should be eliminated before the
> GA.
>
> Could we consider doing a beta release to keep at least a 6-month release
> cadence and also show the community that 4.0.0 GA is the next stop?
>
> Thanks,
> Denys
>


Re: [DISCUSS] HIVE 4.0.0 GA Release Proposal

2023-05-31 Thread Denys Kuzmenko
Hi folks,

The master branch has many new features, bug fixes, and performance 
improvements since alpha-2. However, we still have several correctness bugs 
[HIVE-26654] and performance issues that should be eliminated before the GA. 

Could we consider doing a beta release to keep at least a 6-month release 
cadence and also show the community that 4.0.0 GA is the next stop?

Thanks,
Denys