Fw: [MENTORS] https://www.apache.org/dist/ has been deprecated

[Bikas Saha]

FYI - for the next release

Bikas

Justin Mclean  于2020年3月4日周三 下午5:14写道：

> Hi,
>
> The new URL to use is https://downloads.apache.org. Currently there is a
> redirect in place that should work but it would be be good to double check
> that all is working
>
> The following podling may need to update their download pages:
> Crail
> Daffodil
> DolphinScheduler
> Flagon
> Gobblin
> Hudi
> IoTDB
> Livy
> Milagro
> Pinot
> PonyMail
> ShardingSphere
> Toree
> Training
> Tuweni
> Weex
>
> And there may be others I’ve not identified. If you are a mentor of one of
> these projects please reach out and organise for this to be done.
>
> Thanks,
> Justin
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Livy 0.7.0 based on RC4

[Bikas Saha]

+1

Bikas

From: mingchao zhao 
Sent: Wednesday, January 8, 2020 6:16 PM
To: dev@livy.incubator.apache.org 
Subject: Re: [VOTE] Release Livy 0.7.0 based on RC4

Tested the general functionality of apache-livy-0.7.0-incubat-bin.zip  and
looks good.

+1

On Wed, Jan 8, 2020 at 8:07 PM Yiheng Wang  wrote:

> Check the release files. Looks good.
>
> +1
>
> On Tue, Jan 7, 2020 at 9:25 PM Saisai Shao  wrote:
>
> > This vote is for releasing Livy 0.7.0 based on RC4.
> >
> > This RC mainly fixes the license issue.
> >
> > The vote will be open until Sunday  Jan 12, 23:59 UTC and
> > will pass with a minimum of 3 +1 binding votes and a majority of positive
> > votes.
> >
> > [+1] This release is ready to send to the Incubator PMC for approval
> >
> > [-1] This release is not ready because...
> >
> > This vote is held according to Apache Incubator release policy:
> > https://incubator.apache.org/policy/incubation.html#releases
> >
> > The RC is based on tag v0.7.0-incubating-rc4:
> >
> >
> https://github.com/apache/incubator-livy/commit/664503355d8bae763989ebac087122e306239d54
> >
> > The release files can be found here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc4/
> >
> > The staged maven artifacts can be found here:
> > https://repository.apache.org/content/repositories/orgapachelivy-1013
> >
> > The list of resolved JIRAs in this release can be found here:
> > https://issues.apache.org/jira/projects/LIVY/versions/12345179
> >
> > Thanks
> > Saisai
> >
>

Re: [RESULT][Vote][LIVY-718] Support multi-active high availability in Livy

[Bikas Saha]

Sorry for coming late to this thread.

I have put my comments on the jira ticket here - 
https://issues.apache.org/jira/browse/LIVY-718?focusedCommentId=17004728=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17004728

It would be nice if we could consider the issues raised in the comments and see 
if it makes sense to accommodate for those in the design proposal.

Thanks
Bikas


From: Marco Gaido 
Sent: Wednesday, December 18, 2019 10:52 PM
To: dev@livy.incubator.apache.org 
Subject: Re: [RESULT][Vote][LIVY-718] Support multi-active high availability in 
Livy

Thank you for this proposal and your work. Looking forward to it.
Thanks,
Marco

On Thu, 19 Dec 2019, 07:27 Yiheng Wang,  wrote:

> Hi All
>
> Thanks for participating in the vote. Here's the result:
> +1 (binding)
> ajbozarth
> zjffdu
> mgaido91
> jerryshao
>
> +1 (no-binding)
> 5
>
> The vote passes. I will create subtasks for it.
>
> Thanks
> Yiheng
>
> On Thu, Dec 12, 2019 at 11:30 AM Yiheng Wang  wrote:
>
> > Dear Community
> >
> > I'd like to call a vote on LIVY-718
> >  "Support
> > multi-active high availability in Livy".
> >
> > Currently, Livy only supports single node recovery. This is not
> sufficient
> > in some production environments. In our scenario, the Livy server serves
> > many notebook and JDBC services. We want to make Livy service more
> > fault-tolerant and scalable.
> >
> > There're already some proposals in the community for high availability.
> > But they're not so complete or just for active-standby high availability.
> > So we propose a multi-active high availability design to achieve the
> > following goals:
> >
> >- One or more servers will serve the client requests at the same time.
> >- Sessions are allocated among different servers.
> >- When one node crashes, the affected sessions will be moved to other
> >active services.
> >
> > Please find the design doc here
> > <
> https://docs.google.com/document/d/1bD3qYZpw14_NuCcSGUOfqQ0pqvSbCQsOLFuZp26Ohjc/edit?usp=sharing
> >,
> > which has been reviewed for several weeks.
> >
> > This vote is open until next Wednesday (Dec. 18).
> >
> > [] +1: Accept the proposal
> > [] +0
> > [] -1: I don't think this is a good idea because ...
> >
> > Thank you
> >
> > Yiheng
> >
>

Re: [VOTE] Release Livy 0.7.0 based on RC3

[Bikas Saha]

+1

Bikas


From: Aliaksandr Sasnouskikh 
Sent: Monday, December 23, 2019 11:58 PM
To: dev@livy.incubator.apache.org 
Subject: Re: [VOTE] Release Livy 0.7.0 based on RC3

+1

вт, 24 дек. 2019 г. в 8:11, Saisai Shao :

> The date is overdue, but we still didn't receive enough votes, let me
> extend the due date to Dec 29, 23:59 UTC. Please help to vote.
>
> Best regards,
> Saisai
>
> Saisai Shao  于2019年12月20日周五 下午4:02写道：
>
> > +1 myself.
> >
> > Yiheng Wang  于2019年12月19日周四 上午11:41写道：
> >
> >> Check the release files. Looks good.
> >>
> >> +1
> >>
> >> On Wed, Dec 18, 2019 at 5:25 PM runzhiwang 
> >> wrote:
> >>
> >> > 
> >> >   +1
> >> >  
> >> >  ** release files*
> >> > I verify the apache-livy-0.7.0-incubating-bin.zip by creating session,
> >> > statement, and everything is ok.
> >> >  I also verify the sha512 and asc file. Both look good.
> >> >
> >> >   ** staged maven artifacts **
> >> >  It's ok.
> >> >  
> >> >
> >> >  ** resolved JIRAs **
> >> >  It's ok. I check all the jiras in the commits.
> >> >  
> >> >
> >> > Thanks
> >> > RunzhiWang
> >> >
> >> >
> >> >
> >> >  --原始邮件--
> >> >   发件人:"Saisai Shao" >> >  发送时间:2019年12月18日(星期三) 中午1:58
> >> >  收件人:"dev" >> >
> >> >  主题:[VOTE] Release Livy 0.7.0 based on RC3
> >> >
> >> >
> >> >
> >> > This vote is for releasing Livy 0.7.0 based on RC3.
> >> >
> >> > The vote will be open until Friday Dec 23, 23:59 UTC and
> >> > will pass with a minimum of 3 +1 binding votes and a majority of
> >> positive
> >> > votes.
> >> >
> >> > [+1] This release is ready to send to the Incubator PMC for approval
> >> >
> >> > [-1] This release is not ready because...
> >> >
> >> > This vote is held according to Apache Incubator release policy:
> >> > https://incubator.apache.org/policy/incubation.html#releases
> >> >
> >> > The RC is based on tag v0.7.0-incubating-rc3:
> >> >
> >> >
> >>
> https://github.com/apache/incubator-livy/commit/0cc431a7e9236e313f9904ef121cad5df444d4da
> >> >
> >> > The release files can be found here:
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.0-incubating-rc3/
> >> >
> >> > The staged maven artifacts can be found here:
> >> > https://repository.apache.org/content/repositories/orgapachelivy-1012
> >> >
> >> > The list of resolved JIRAs in this release can be found here:
> >> > https://issues.apache.org/jira/projects/LIVY/versions/12345179
> >> >
> >> > Thanks
> >> > Saisai
> >>
> >
>
--
Отправлено с мобильного устройства

Re: Podling Report Reminder - October 2019

[Bikas Saha]

Lets see if we get any specific guidance from the Board based on the report.

Bikas


From: Alex Bozarth 
Sent: Tuesday, October 1, 2019 3:28 PM
To: dev@livy.incubator.apache.org 
Subject: RE: Podling Report Reminder - October 2019


I agree based on the stability of the community over the past year that 
discussing a potential graduation has merit.


Alex Bozarth
Software Engineer
Center for Open-Source Data & AI Technologies

E-mail: ajboz...@us.ibm.com<mailto:ajboz...@us.ibm.com>
GitHub: github.com/ajbozarth<https://github.com/ajbozarth>


505 Howard Street
San Francisco, CA 94105
United States



[Inactive hide details for Bikas Saha ---09/30/2019 08:18:38 PM---Hi, The issue 
seems to have resolved itself. Coming to why I s]Bikas Saha ---09/30/2019 
08:18:38 PM---Hi, The issue seems to have resolved itself. Coming to why I 
started the edit.

From: Bikas Saha 
To: "dev@livy.incubator.apache.org" 
Date: 09/30/2019 08:18 PM
Subject: [EXTERNAL] Re: Podling Report Reminder - October 2019





Hi,

The issue seems to have resolved itself. Coming to why I started the edit.

Please see my note under the Livy section so that we can discuss if it makes 
sense or not.
https://cwiki.apache.org/confluence/display/INCUBATOR/October2019#three-most-important-unfinished-issues-to-address-before-graduating-7

Essentially, IMO, I see the Apache Livy community and code practices following 
the tenets of the Apache way. The community also has multiple public releases 
following due process. There has been addition of new contributors and 
committers based on their participation. Based on that I feel we could start a 
conversation on whether the project is ready to graduate.

There is no doubt that the code and community activity is not as voluminous as 
some of the larger projects like Apache Hadoop or Spark. But those projects 
also have a significantly larger scope in terms of features/functionality 
compared to Livy. So it may be that, as of now, Apache Livy is a stable project 
that meets its intended scope. Thus its ok for it to have moderate code and 
community activity until such time as new scope/features are identified which 
would spurt the next wave of high activity.

With the above context, does it make sense to discuss whether the project is 
ready to graduate with its current (relative small) community.

Thoughts?
Bikas


From: Jean-Baptiste Onofré 
Sent: Sunday, September 22, 2019 10:31 PM
To: dev@livy.incubator.apache.org 
Subject: Re: Podling Report Reminder - October 2019

Hi,

it works fine for me.

Regards
JB

On 22/09/2019 18:47, Bikas Saha wrote:
> Hi,
>
> I noticed the wiki page said this wiki has been enabled with LDAP and login 
> with Apache credentials. I did and it logged me in but reported an error on 
> every link saying I don't have permissions. Anyone else hitting this issue?
>
> Bikas
>
> 
> From: jmcl...@apache.org 
> Sent: Sunday, September 22, 2019 3:46 AM
> To: dev@livy.incubator.apache.org 
> Subject: Podling Report Reminder - October 2019
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 October 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, October 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page 

Re: Podling Report Reminder - October 2019

[Bikas Saha]

Hi,

The issue seems to have resolved itself. Coming to why I started the edit.

Please see my note under the Livy section so that we can discuss if it makes 
sense or not.
https://cwiki.apache.org/confluence/display/INCUBATOR/October2019#three-most-important-unfinished-issues-to-address-before-graduating-7

Essentially, IMO, I see the Apache Livy community and code practices following 
the tenets of the Apache way. The community also has multiple public releases 
following due process. There has been addition of new contributors and 
committers based on their participation. Based on that I feel we could start a 
conversation on whether the project is ready to graduate.

There is no doubt that the code and community activity is not as voluminous as 
some of the larger projects like Apache Hadoop or Spark. But those projects 
also have a significantly larger scope in terms of features/functionality 
compared to Livy. So it may be that, as of now, Apache Livy is a stable project 
that meets its intended scope. Thus its ok for it to have moderate code and 
community activity until such time as new scope/features are identified which 
would spurt the next wave of high activity.

With the above context, does it make sense to discuss whether the project is 
ready to graduate with its current (relative small) community.

Thoughts?
Bikas


From: Jean-Baptiste Onofré 
Sent: Sunday, September 22, 2019 10:31 PM
To: dev@livy.incubator.apache.org 
Subject: Re: Podling Report Reminder - October 2019

Hi,

it works fine for me.

Regards
JB

On 22/09/2019 18:47, Bikas Saha wrote:
> Hi,
>
> I noticed the wiki page said this wiki has been enabled with LDAP and login 
> with Apache credentials. I did and it logged me in but reported an error on 
> every link saying I don't have permissions. Anyone else hitting this issue?
>
> Bikas
>
> 
> From: jmcl...@apache.org 
> Sent: Sunday, September 22, 2019 3:46 AM
> To: dev@livy.incubator.apache.org 
> Subject: Podling Report Reminder - October 2019
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 October 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, October 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/October2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Podling Report Reminder - October 2019

[Bikas Saha]

Hi,

I noticed the wiki page said this wiki has been enabled with LDAP and login 
with Apache credentials. I did and it logged me in but reported an error on 
every link saying I don't have permissions. Anyone else hitting this issue?

Bikas


From: jmcl...@apache.org 
Sent: Sunday, September 22, 2019 3:46 AM
To: dev@livy.incubator.apache.org 
Subject: Podling Report Reminder - October 2019

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 October 2019, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, October 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/October2019

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Report Reminder - April 2019

[Bikas Saha]

 Hi,

I have updated the report. Please review.

Also it would help if someone could add the last release date. While
transitioning mailboxes I have lost my older emails. So I could not look up
the date. Of course, if 0.6 lands before the last reporting date then we
can modify the report with the new release.

Thanks
Bikas

On Sat, Mar 23, 2019 at 6:28 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 17 April 2019, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, April 03).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://wiki.apache.org/incubator/April2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Report Reminder - October 2018

[Bikas Saha]

Hi All,

Any volunteers for the podling report?

Seems like the JDBC feature is worth mentioning, among other regular stuff.

Thanks
Bikas


From: jmcl...@apache.org 
Sent: Sunday, September 23, 2018 12:47 PM
To: dev@livy.incubator.apache.org
Subject: Podling Report Reminder - October 2018

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 17 October 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, October 03).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/October2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling report this month

[Bikas Saha]

Done!

Bikas


From: Saisai Shao 
Sent: Sunday, July 8, 2018 7:17 PM
To: dev@livy.incubator.apache.org
Subject: Re: Podling report this month

Updated. Please review and sign off.

Thanks

Saisai Shao  于2018年7月9日周一 上午8:27写道：

> Sorry I forgot about this, will draft this today.
>
> Thanks
> Saisai
>
> Jean-Baptiste Onofré  于2018年7月8日周日 下午1:17写道：
>
>> Hi guys,
>>
>> we have to report this month:
>>
>> https://wiki.apache.org/incubator/July2018
>>
>> Did someone already start a report ? I can bootstrap one if you want.
>>
>> Thanks,
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

Re: [VOTE] Livy 0.5.0-incubating (RC2)

[Bikas Saha]

Late landing +1.

Bikas


From: Alex Bozarth 
Sent: Thursday, January 25, 2018 3:57 PM
To: dev@livy.incubator.apache.org
Subject: [VOTE] Livy 0.5.0-incubating (RC2)



Hey team,

Now that the security vulnerability that was found has been addressed, RC2
of Livy 0.5.0-incubating is ready for testing and approval.


The vote will be open 72 hours until Monday January 29th at 12:00AM UTC and
will pass with a minimum of 3 +1 votes and a majority of positive votes.

[+1] This release is ready to send to the Incubator PMC for approval

[-1] This release is not ready because...

This vote is held according to Apache Incubator release policy:
https://incubator.apache.org/policy/incubation.html#releases

This release files can be found here:
https://dist.apache.org/repos/dist/dev/incubator/livy/0.5.0-incubating-rc2/

The list of resolved JIRAs in this release can be found here:
https://issues.apache.org/jira/projects/LIVY/versions/12341543


I will also include my own +1 here



 Alex Bozarth
 Software Engineer
 Spark Technology Center




 E-mail: ajboz...@us.ibm.com
 GitHub: github.com/ajbozarth
   505 Howard 
Street
 San Francisco, CA 
94105
   United 
States

Re: 0.5-incubating release timing

[Bikas Saha]

Looks like I am also not an admin on the Project. Let me see if I can fix the 
released label.

Bikas

From: Alex Bozarth 
Sent: Tuesday, January 16, 2018 12:32 PM
To: dev@livy.incubator.apache.org
Subject: 0.5-incubating release timing



Hey team,

So with LIVY-104 wrapping up today and LIVY-141/LIVY-175 wrapping up later
this week I don't see any other open PRs that are aimed for 0.5. With that
in mind, do we want to plan on cutting RC1 at the end of the week?

On a related note, 0.4 is still not marked as "released" in the Apache
JIRA, could someone with Admin privileges can update that?


 Alex Bozarth
 Software Engineer
 Spark Technology Center




 E-mail: ajboz...@us.ibm.com
 GitHub: github.com/ajbozarth
   505 Howard 
Street
 San Francisco, CA 
94105
   United 
States

Re: [DRAFT] Incubator PMC Board Report - January 2018

[Bikas Saha]

 2017 Global Internet Technology
Conference (Speaker: Lei Chang, Nov 24, 2017)


2. Active contributions from approximately 20 different community
  contributors since the last report.

3. Three committer candidates passed the voting process:

  1) Amy BAI
  2) ChunLing WANG
  3) Hongxu MA


How has the project developed since the last report?


1. The scope of 2.3 release is finalized, and is under development

 1) New Feature: HAWQ Ranger supports RPS HA.  (Done)
 2) New Feature: HAWQ Ranger supports Kerberos authentication. (Done)
 3) New Feature: HAWQ Core supports plugable external storage framework.
(Almost Done HAWQ-786)
 4) New Feature: HAWQ Core supports HDFS TDE (Transparent Data Encryption)
through libHdfs3. (Done, HAWQ-1193)
 5) Licenses: Fix PXF license files located in PXF jar files. (Done
HAWQ-1496)
 6) Licenses: Check Apache HAWQ mandatory libraries to match LC20, LC30
license criteria. (Not started HAWQ-1512)
 7) Build: Release build project (On going HAWQ-127)
 8) Bug fixes. (On going)

Project page link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_HAWQ_Apache-2BHAWQ-2B2.3.0.0-2Dincubating-2BRelease=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=EiINg_pD-OOs2NCf27vgOHFQscJtM7a4mwftG_PoIeY=-pw2t8Ekv7dkI_hcDINoCu9FmINcJoQCsVrPWRO8s84=


2. The community discussed the future of PXF with the addition of the
pluggable storage feature: Pluggable storage formats and files systems vs.
PXF


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [X] Nearing graduation
 [ ] Other:

Date of last release:

 2017-07-12, Apache HAWQ 2.2.0.0

When were the last committers or PPMC members elected?

  1) Amy BAI:  Nov 1, 2017
  2) ChunLing WANG: Nov 1, 2017
  3) Hongxu MA: Nov 4, 2017


Signed-off-by:

 [ ](hawq) Alan Gates
Comments:
 [ ](hawq) Konstantin Boudnik
Comments:
 [ ](hawq) Justin Erenkrantz
Comments:
 [ ](hawq) Thejas Nair
Comments:
 [X](hawq) Roman Shaposhnik
Comments:


IPMC/Shepherd notes:




HTrace

HTrace is a tracing framework intended for use with distributed systems
written in java.

HTrace has been incubating since 2014-11-11.

Three most important issues to address in the move towards graduation:

 1.
 2.
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

 [ ](htrace) Jake Farrell
Comments:
 [ ](htrace) Todd Lipcon
Comments:
 [ ](htrace) Lewis John Mcgibbney
Comments:
 [ ](htrace) Andrew Purtell
Comments:
 [ ](htrace) Billie Rinaldi
Comments:
 [ ](htrace) Michael Stack
Comments:

IPMC/Shepherd notes:




Livy

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important issues to address in the move towards graduation:

 1.
 2.
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 -XX-XX

When were the last committers or PPMC members elected?



Signed-off-by:

 [ ](livy) Bikas Saha
Comments:
 [ ](livy) Brock Noland
Comments:
 [ ](livy) Luciano Resende
Comments:
 [ ](livy) Jean-Baptiste Onofre
Comments:

IPMC/Shepherd notes:




Milagro

Distributed Cryptography; M-Pin protocol for Identity and Trust

Milagro has been incubating since 2015-12-21.

Three most important issues to address in the move towards graduation:

 1.
 2.
 3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 -XX-XX

When were the last committers or PPMC member

Re: user defined sessionId / URI for Livy sessions

[Bikas Saha]

Resending to both aliases

Hi,

Would be good to understand how this feature would be useful other than 
providing users a handle that they can rely on as a 3rd party.

E.g. something like this may be useful in an active-active livy configuration 
because its not clear how sequential numeric id's would work in that context. 
Perhaps UUID's would also suffice for the active-active setup. Maybe the use 
case for user defined sessions could be to integrate with other software that 
could reliably use the user defined name for its internal operations instead of 
using a livy session id thats not guaranteed to be unique.

Curious as to what motivated choosing sequential numbers for livy sessions?

Bikas



From: Alex Bozarth 
Sent: Tuesday, September 12, 2017 2:44 PM
To: u...@livy.incubator.apache.org
Cc: dev@livy.incubator.apache.org
Subject: Re: user defined sessionId / URI for Livy sessions


That's fair, I'll still withhold judgement until I see an impl though.



Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com
GitHub: github.com/ajbozarth


505 Howard Street
San Francisco, CA 94105
United States




[Inactive hide details for Marcelo Vanzin ---09/12/2017 02:40:33 PM---BTW take 
my comment there with a grain of salt; at the tim]Marcelo Vanzin ---09/12/2017 
02:40:33 PM---BTW take my comment there with a grain of salt; at the time Livy 
was being targeted at mostly being

From: Marcelo Vanzin 
To: dev@livy.incubator.apache.org
Cc: "u...@livy.incubator.apache.org" 
Date: 09/12/2017 02:40 PM
Subject: Re: user defined sessionId / URI for Livy sessions





BTW take my comment there with a grain of salt; at the time Livy was being 
targeted at mostly being hidden from users, making such a feature not make much 
sense in Livy itself. But things may have changed since then, especially as 
people started using it more.

On Mon, Sep 11, 2017 at 1:51 PM, Alex Bozarth 
> wrote:

I would agree with Marcelo's comment the JIRA that this isn't a good feature 
for livy, but I'll take a look at your impl if you open a PR and see if it 
changes my mind.


Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com
GitHub: 
github.com/ajbozarth


505 Howard Street
San Francisco, CA 94105
United States




Meisam Fathi ---09/11/2017 10:23:49 AM---+ dev Is there any interest in adding 
this feature to Livy? I can send a PR

From: Meisam Fathi >
To: "u...@livy.incubator.apache.org" 
>, 
"dev@livy.incubator.apache.org" 
>
Date: 09/11/2017 10:23 AM
Subject: Re: user defined sessionId / URI for Livy sessions




+ dev
Is there any interest in adding this feature to Livy? I can send a PR

Ideally, it would be helpful if we could mint a session ID with a PUT
> request, something like PUT /sessions/foobar, where "foobar" is the newly
> created sessionId.
>
> I suggest we make session names unique and nonnumeric values (to guarantee
a session name does not clash with another session name or session ID).

Design doc:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_meisam_incubator-2Dlivy_wiki_Design-2Ddoc-2Dfor-2DLivy-2D41-3A-2DAccessing-2Dsessions-2Dby-2Dname=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=bUJg_csAaA5f2DPiMkjU-juQkf5Q2FMYtA5kv5sqiMM=xTiY52FMWMdTRgCmiNRWe6yEoCchxKNxQrYPEkPupbw=
JIRA ticket: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_LIVY-2D41=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=bUJg_csAaA5f2DPiMkjU-juQkf5Q2FMYtA5kv5sqiMM=lFed2hYlDA_wUo94RWUAw7N01lSN368P-ABmP_npWrM=


Thanks,
Meisam






--
Marcelo

Re: [DISCUSS] Release Cadence

[Bikas Saha]

Hi,

If 3 months is agreeable then November would be on the plate. I think the 
shared context across languages is a super useful user feature that could be 
released. Any other features that could go in for that time frame?

Bikas


From: Alex Bozarth <ajboz...@us.ibm.com>
Sent: Wednesday, September 6, 2017 2:05 PM
To: dev@livy.incubator.apache.org
Subject: Re: [DISCUSS] Release Cadence


I'm ok with 3 months, and I agree about the December issue, would you suggest a 
November release then or wait until January?


Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com<mailto:ajboz...@us.ibm.com>
GitHub: github.com/ajbozarth<https://github.com/ajbozarth>


505 Howard Street
San Francisco, CA 94105
United States




[Inactive hide details for Bikas Saha ---09/06/2017 02:01:26 PM---Hi, 4 months 
might be too long for a relatively new project li]Bikas Saha ---09/06/2017 
02:01:26 PM---Hi, 4 months might be too long for a relatively new project like 
Livy. And doing a release in Decemb

From: Bikas Saha <bikas.apa...@outlook.com>
To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org>
Date: 09/06/2017 02:01 PM
Subject: Re: [DISCUSS] Release Cadence





Hi,

4 months might be too long for a relatively new project like Livy. And doing a 
release in December might not be easy with that being holiday season in many 
places.

I was thinking of following Spark's history of 3 month releases initially. That 
provides about 2 months of feature development work followed by 1 month of time 
to start a release, go through bug fixes and finish the process. To be clear, 
that would be for major releases like 0.5, 0.6 etc.

If sufficient bug fixes accumulate much earlier than that then a minor bug fix 
release could be done ahead of time, like you suggest. Specially if these end 
up being security fixes.

Bikas


From: Alex Bozarth <ajboz...@us.ibm.com>
Sent: Wednesday, September 6, 2017 1:54 PM
To: dev@livy.incubator.apache.org
Subject: Re: [DISCUSS] Release Cadence


I think we discussed this some in a previous chain and came to the general 
consensus that a time based release cadence was best but didn't settle on the 
cadence length. Personally I think every 4 months (thus our next release around 
new years) would work well and give us flexibility to release a bit early or 
late to match with a Spark release if necessary. I would say every 6 months 
based on our previous release rate, but I think that cadence is too long if we 
want the project to continue to gain momentum. As for maintenance/patch 
releases I think we should release whenever there's enough fixes to warrant it.


Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com<mailto:ajboz...@us.ibm.com>
GitHub: 
github.com/ajbozarth<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=E5PTfuFmbFjYDn2SKKQ0eTbeQ__nwGToXjZeG5BGQ-8=MKOBWohtx6XyGFWKBIof5c3fv-RfVu6MLo2QHN1H5u8=
 >


505 Howard Street
San Francisco, CA 94105
United States




[Inactive hide details for Bikas Saha ---09/06/2017 01:42:11 PM---Hi, We just 
did our first release and hopefully have ironed ou]Bikas Saha ---09/06/2017 
01:42:11 PM---Hi, We just did our first release and hopefully have ironed out 
the release mechanics and also provi

From: Bikas Saha <bi...@apache.org>
To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org>
Date: 09/06/2017 01:42 PM
Subject: [DISCUSS] Release Cadence





Hi,

We just did our first release and hopefully have ironed out the release 
mechanics and also provided users a transition point to move over their 
dependencies to ASF.

I think now would be a good time to figure out our release mechanics.

IMO time based release mechanics have worked out well for projects like Apache 
Spark. Regular releases allow for timely updates with bug fixes for increased 
stability. Also, they reduce unnecessary angst around features making into 
release because there is always the next timely release to latch on to in case 
the current release is missed.

Are there other things to consider? E.g. making a concurrent release (even if 
its ad-hoc) to match Apache Spark releases because there is a strong dependency 
on the project. That would depend on whether we depend/integrate with new 
features in that Spark release.

Thanks
Bikas

Re: [DISCUSS] Release Cadence

[Bikas Saha]

Hi,

4 months might be too long for a relatively new project like Livy. And doing a 
release in December might not be easy with that being holiday season in many 
places.

I was thinking of following Spark's history of 3 month releases initially. That 
provides about 2 months of feature development work followed by 1 month of time 
to start a release, go through bug fixes and finish the process. To be clear, 
that would be for major releases like 0.5, 0.6 etc.

If sufficient bug fixes accumulate much earlier than that then a minor bug fix 
release could be done ahead of time, like you suggest. Specially if these end 
up being security fixes.

Bikas


From: Alex Bozarth <ajboz...@us.ibm.com>
Sent: Wednesday, September 6, 2017 1:54 PM
To: dev@livy.incubator.apache.org
Subject: Re: [DISCUSS] Release Cadence


I think we discussed this some in a previous chain and came to the general 
consensus that a time based release cadence was best but didn't settle on the 
cadence length. Personally I think every 4 months (thus our next release around 
new years) would work well and give us flexibility to release a bit early or 
late to match with a Spark release if necessary. I would say every 6 months 
based on our previous release rate, but I think that cadence is too long if we 
want the project to continue to gain momentum. As for maintenance/patch 
releases I think we should release whenever there's enough fixes to warrant it.


Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com<mailto:ajboz...@us.ibm.com>
GitHub: github.com/ajbozarth<https://github.com/ajbozarth>


505 Howard Street
San Francisco, CA 94105
United States




[Inactive hide details for Bikas Saha ---09/06/2017 01:42:11 PM---Hi, We just 
did our first release and hopefully have ironed ou]Bikas Saha ---09/06/2017 
01:42:11 PM---Hi, We just did our first release and hopefully have ironed out 
the release mechanics and also provi

From: Bikas Saha <bi...@apache.org>
To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org>
Date: 09/06/2017 01:42 PM
Subject: [DISCUSS] Release Cadence





Hi,

We just did our first release and hopefully have ironed out the release 
mechanics and also provided users a transition point to move over their 
dependencies to ASF.

I think now would be a good time to figure out our release mechanics.

IMO time based release mechanics have worked out well for projects like Apache 
Spark. Regular releases allow for timely updates with bug fixes for increased 
stability. Also, they reduce unnecessary angst around features making into 
release because there is always the next timely release to latch on to in case 
the current release is missed.

Are there other things to consider? E.g. making a concurrent release (even if 
its ad-hoc) to match Apache Spark releases because there is a strong dependency 
on the project. That would depend on whether we depend/integrate with new 
features in that Spark release.

Thanks
Bikas

[DISCUSS] Release Cadence

[Bikas Saha]

Hi,

We just did our first release and hopefully have ironed out the release 
mechanics and also provided users a transition point to move over their 
dependencies to ASF.

I think now would be a good time to figure out our release mechanics.

IMO time based release mechanics have worked out well for projects like Apache 
Spark. Regular releases allow for timely updates with bug fixes for increased 
stability. Also, they reduce unnecessary angst around features making into 
release because there is always the next timely release to latch on to in case 
the current release is missed.

Are there other things to consider? E.g. making a concurrent release (even if 
its ad-hoc) to match Apache Spark releases because there is a strong dependency 
on the project. That would depend on whether we depend/integrate with new 
features in that Spark release.

Thanks
Bikas

Re: The process of Livy 0.4.0-incubating release

[Bikas Saha]

This is great! We have a first release.

I will start a thread on general release cadence.

Bikas


From: Alex Bozarth 
Sent: Monday, September 4, 2017 9:43 AM
To: dev@livy.incubator.apache.org
Subject: Re: The process of Livy 0.4.0-incubating release


Thanks Jerry, I think we're good to announce.


Alex Bozarth
Software Engineer
Spark Technology Center


E-mail: ajboz...@us.ibm.com
GitHub: github.com/ajbozarth


505 Howard Street
San Francisco, CA 94105
United States




[Inactive hide details for Saisai Shao ---09/03/2017 08:05:24 PM---Hi all, All 
the stuffs related to 0.4.0-incubating release ar]Saisai Shao ---09/03/2017 
08:05:24 PM---Hi all, All the stuffs related to 0.4.0-incubating release are 
done, please check.

From: Saisai Shao 
To: dev@livy.incubator.apache.org
Date: 09/03/2017 08:05 PM
Subject: Re: The process of Livy 0.4.0-incubating release





Hi all,

All the stuffs related to 0.4.0-incubating release are done, please check.

If you don't mind I'm going to announce the release of Livy
0.4.0-incubating in the incubation mail list.

Thanks
Jerry



On Sat, Sep 2, 2017 at 2:11 AM, Alex Bozarth  wrote:

> The website PRs are updated (with a 9/1/17 release date) and ready to
> merge.
>
> @jerry if you want to merge them and update the website when you send the
> announcement email.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* 
> *GitHub: **github.com/ajbozarth* 
>   >
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Saisai Shao ---09/01/2017 01:11:03
> AM---Hi all, I just published maven artifacts to repository.apache]Saisai
> Shao ---09/01/2017 01:11:03 AM---Hi all, I just published maven artifacts
> to repository.apache.org, please check 
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=hUGxrkJa6yavXNv9UWSQkfuKkU67CuDR_DNeZGEQa7g=oUMtC2kpv7Q_9MwJtfgMskUp5m_gemA8nugCG_8hm3A=
>  .
>
> From: Saisai Shao 
> To: dev@livy.incubator.apache.org
> Date: 09/01/2017 01:11 AM
> Subject: Re: The process of Livy 0.4.0-incubating release
> --
>
>
>
> Hi all, I just published maven artifacts to repository.apache.org, please
> check (https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__repository.apache.org_-23nexus-2Dsearch-3Bquick-
> 7Eorg.apache.livy=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_
> S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=fMV22rxtZ56xBOsS_
> 08nAtWN0INQGs6rwMRoj1ot8js=PDM5YGd_nH5qlIketLl_
> Igr0Fhdqyf9IsI1QIwwEq4M= ).
>
> I think once related doc is updated, all the release work should be done.
>
> Thanks
> Jerry
>
>
>
> On Thu, Aug 31, 2017 at 9:01 AM, Alex Bozarth  wrote:
>
> > I agree with Jeff on the announcement timing, the links on the website PR
> > are already updated and working, I'll just have to push an update to the
> > release date once we know when we'll announce the release. And you can
> > delete the gh-pages branch, it's been moved to the old-site branch on the
> > website repo.
> >
> >
> > *Alex Bozarth*
> > Software Engineer
> > Spark Technology Center
> > --
> > *E-mail:* *ajboz...@us.ibm.com* 
> > *GitHub: **github.com/ajbozarth* 
> >  >  .> proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=
> DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-
> cx37DPYDyo=fMV22rxtZ56xBOsS_08nAtWN0INQGs6rwMRoj1ot8js=
> CzCDePcP9HxXc4FCCima2ThJ0zgF6K5oHcRKWJEegMg= >
> >
> >
> > 505 Howard Street
> > San Francisco, CA 94105
> > United States
> >
> >
> >
> > [image: Inactive hide details for Jeff Zhang ---08/30/2017 05:53:15
> PM---I
> > think we'd better to announce after the artifacts are publis]Jeff Zhang
> > ---08/30/2017 05:53:15 PM---I think we'd better to announce after the
> > artifacts are published. Saisai Shao  >
> > From: Jeff Zhang 
> > To: dev@livy.incubator.apache.org
> > Date: 08/30/2017 05:53 PM
> > Subject: Re: The process of Livy 0.4.0-incubating release
> > --
>
> >
> >
> >
> > I think we'd better to announce after the artifacts are 

Re: The process of Livy 0.4.0-incubating release

[Bikas Saha]

IIRC it would be maven with the org.apache coordinates.


Wait for it to be available via caches. Then we can update the website and send 
out a notice email to the lists.


Bikas


From: Saisai Shao 
Sent: Sunday, August 27, 2017 11:53:45 PM
To: dev@livy.incubator.apache.org
Subject: The process of Livy 0.4.0-incubating release

Hi mentors,

Would you please guide us on how to release the Livy 0.4.0-incubating,
including artifact publish.

Also regarding push artifacts to repo, are we inclining to change to Maven
central repo, or we still use Cloudera repo, any suggestion?

Besides, for Python package release, do we need to publish this python
client package to PIP or we don't need to do this now, any comment?

Thanks for your help and suggestion.

Best regards,
Saisai (Jerry)

Re: [VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

[Bikas Saha]

+1 (binding)


Built from source and ran some local tests manually. Spot checked a few random 
files for license and attribution.


Bikas



From: Marcelo Vanzin 
Sent: Wednesday, August 23, 2017 9:04:46 AM
To: gene...@incubator.apache.org
Cc: dev@livy.incubator.apache.org
Subject: Re: [VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

Just echoing my +1 from the Livy list.

On Tue, Aug 22, 2017 at 12:33 AM, Jerry Shao  wrote:
> Hello Incubator PMC’ers,
>
> The Apache Livy community has decided to release Apache Livy
> 0.4.0-incubating based on 0.4.0-incubating Release Candidate 2. We now
> kindly request the Incubator PMC members to review and vote on this incubator
> release.
>
> Livy is web service that exposes a REST interface for managing long running
> Apache Spark contexts in your cluster. With Livy, new applications can be
> built on top of Apache Spark that require fine grained interaction with
> many Spark contexts.
>
> Artifacts are available at
> https://dist.apache.org/repos/dist/dev/incubator/livy/, public keys are
> available at https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS.
>
> livy-0.4.0-incubating-src.zip <
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-src-RC2.zip
>> is a source release. Along with it, for convenience, please find the
> binary release as livy-0.4.0-incubating-bin-RC2.zip <
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-bin-RC2.zip
>>.
>
>
> Git tag:
> *https://github.com/apache/incubator-livy/releases/tag/v0.4.0-incubating-rc2
> *
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Members please be sure to indicate "(Binding)" with your vote which will
> help in tallying the vote(s).
>
> * Here is my +1 (non-binding) *
>
> Cheers,
> Jerry



--
Marcelo