Re: Podling Livy Report Reminder - July 2020
@jerry could you take care of this? I'm about to leave on vacation and this is due before I get back. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: jmcl...@apache.org To: dev@livy.incubator.apache.org Date: 06/24/2020 08:52 PM Subject:[EXTERNAL] Podling Livy Report Reminder - July 2020 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, 15 July 2020. 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, July 01). 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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_INCUBATOR_July2020=DwICAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=ip7h4dzeq1V5oOj2J91I3ho6K9ck8H6eCmOTN6wbplg=Ubfm5XROltUlJyWYki-MybY7nza6SXQomhI5zbidwkQ= 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 Livy Report Reminder - April 2020
@jerry: you think you can handle this? It's due Wednesday an you've been more active on Livy in the last few month than me. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: jmcl...@apache.org To: dev@livy.incubator.apache.org Date: 03/25/2020 04:20 PM Subject:[EXTERNAL] Podling Livy Report Reminder - April 2020 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, 15 April 2020, 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 01). 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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_INCUBATOR_April2020=DwICAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=ec9a4r5zUw7hwUFd0qYuWa3JXzitmJwTGaLLMbj6VV0=BX39VNJNbwIJL5P7eFHM5NHYxFPK6HFTk1moCtH8-9U= 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: Possible missing mentor(s)
Sorry for my delayed weigh-in as a committer, I was on (a rare) vacation. As for the discussion, I agree with Marco's points. As far as I go, the PR's I've been pinged on are either WIP or changes were requested and then left hanging. Also as many have said, if I'm not pinged I don't usually check on open PRs since I haven't have bandwidth for Livy development recently. For PRs I do believe things could be better, but I also believe that Livy's handling of open PRs is approximately the same as other projects like Spark (not to say that's necessarily a positive). It also may be time to start pruning hanging PRs: pinging creators on PRs left with unaddressed change requests and closing them if there's no response in a set time, closing PRs that have been discussed and seemingly rejected, requesting reviewers for PRs that are active but without reviews. This is something Spark does regularly but after 2 years we've yet to do. We could also offer the dev list an opportunity to resurrect PRs abandoned by their original dev before closing them if another dev wants to continue work on it. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Marco Gaido To: dev@livy.incubator.apache.org Cc: Sid Anand Date: 09/02/2019 02:01 AM Subject:[EXTERNAL] Re: Possible missing mentor(s) Sid, answering to the PRs you pointed out, I think open meisam's PRs are: - 1 WIP; - 1 changes were requested and he has not done them; - 1 I commented on it and it was stated that the feature could have been merged if the PR is brought up to date, which hasn't so far by the contributor. Moreover, I have never seen on the PRs committers getting pinged. IMHO, those PRs are stuck due to the inactivity of the contributor. Surely we have to do more in order to be able to review more PRs, but, as Saisai said, we are stil a small community with few active committers, so we try and do our best. More importantly, I think there is really no evidence at all of the alleged bias. In general, I think we all know that you need to be very active in the community to avoid PRs getting stale. This is true also for bigger communities like Spark. So what I'd encourage is also more proactivity by the contributors. I think the message should not be: "I open a PR and committer must immediately merge it"; but "I open a PR, I ask for committers' help on reviews and try and push in order to have it in if the PR is important". Thanks, Marco Il giorno dom 1 set 2019 alle ore 20:52 Pat Ferrel ha scritto: > Seems like some action should be taken before 2 years, even if it is to > close the PR because it is not appropriate. Isn’t this the responsibility > of the chair to guard against committer changes where the contributor is > still willing? Or if a mentor is guiding the PR they should help it get > unstalled if the contributor is still willing to make changes. > > The point (2 year old PRs) seems well taken. The question should be; what > can be done about this? > > For what it’s worth, we are just starting to use Livy and wish it was part > of Spark. We would like to treat Spark as a “microservice” as a compute > engine. The Spark team seems to want to make Spark integral to the > architecture of ALL applications that use it. Very odd from our point of > view. > > So to integrate Livy we deeply hope it doesn’t fall into disrepair and are > willing to help when we run into something. > > > From: Sid Anand > Reply: dev@livy.incubator.apache.org > > Date: September 1, 2019 at 11:19:00 AM > To: dev@livy.incubator.apache.org > > Subject: Re: Possible missing mentor(s) > > "Second, if someone has a *good* and *large* contribution history, and > actively participates i
0.6 release cleanup
I was just looking at the GitHub repo and noticed that the rc tags are still there. They probably should have been deleted once the release was cut. @marcelo do you want to do the cleanup since you cut the release? Otherwise I can take care of it when I have some time later on. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States
Re: [VOTE] Move source repo to gitbox
+1 from me Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Marcelo Vanzin To: dev@livy.incubator.apache.org Date: 01/03/2019 09:57 AM Subject:[VOTE] Move source repo to gitbox Creating a formal vote for this. I don't think we have a choice but they seem to request a vote anyway. This will be lazy consensus, I plan to create an infra ticket for the migration on Monday if the vote passes. Starting with my +1. -- Marcelo
Re: GitHub emails on dev
That's a good idea, how would we go about doing that? Ask infra or can a mentor do it? And what kind of approval would we need? Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Luciano Resende To: dev@livy.incubator.apache.org Date: 10/08/2018 06:02 PM Subject:Re: GitHub emails on dev You guys should create a list and have these forwarded to the new list. Some projects use notifications@ On Mon, Oct 8, 2018 at 17:46 Alex Bozarth wrote: > I opened https://issues.apache.org/jira/browse/INFRA-17121 for INFRA to > take a look into it. > > > *Alex Bozarth* > Software Engineer > Center for Open-Source Data & AI Technologies > -- > *E-mail:* *ajboz...@us.ibm.com* > *GitHub: **github.com/ajbozarth* < https://github.com/ajbozarth > > > > 505 Howard Street > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > San Francisco, CA 94105 > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > United States > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > > > > [image: Inactive hide details for Marcelo Vanzin ---10/08/2018 04:23:04 > PM---Maybe infra did something to re-enable it. We asked them t]Marcelo > Vanzin ---10/08/2018 04:23:04 PM---Maybe infra did something to re-enable > it. We asked them to disable it way back (INFRA-14973). Maybe > > From: Marcelo Vanzin > To: dev@livy.incubator.apache.org > Date: 10/08/2018 04:23 PM > Subject: Re: GitHub emails on dev > -- > > > > > Maybe infra did something to re-enable it. We asked them to disable it > way back (INFRA-14973). Maybe reopen that ticket or file a new one. > On Mon, Oct 8, 2018 at 4:19 PM Alex Bozarth wrote: > > > > > > > > Is there a reason we've begun getting GitHub PR emails on the dev list? > The > > regular glut of emails for every comment on every PR probably shouldn't > be > > CC'd to dev@ > > > > > > Alex Bozarth > > Software Engineer > > Center for Open-Source Data & AI Technologies > > > > > > > > > > E-mail: ajboz...@us.ibm.com > > GitHub: github.com/ajbozarth > >505 > Howard Street > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > > San > Francisco, CA 94105 > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > > United > States > < https://maps.google.com/?q=505+Howard+Street+San+Francisco,+CA+94105+United+States=gmail=g > > > > > > > > > > > > > > -- > Marcelo > > > > > -- Sent from my Mobile device
Re: GitHub emails on dev
I opened https://issues.apache.org/jira/browse/INFRA-17121 for INFRA to take a look into it. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Marcelo Vanzin To: dev@livy.incubator.apache.org Date: 10/08/2018 04:23 PM Subject:Re: GitHub emails on dev Maybe infra did something to re-enable it. We asked them to disable it way back (INFRA-14973). Maybe reopen that ticket or file a new one. On Mon, Oct 8, 2018 at 4:19 PM Alex Bozarth wrote: > > > > Is there a reason we've begun getting GitHub PR emails on the dev list? The > regular glut of emails for every comment on every PR probably shouldn't be > CC'd to dev@ > > > Alex Bozarth > Software Engineer > Center for Open-Source Data & AI Technologies > > > > > E-mail: ajboz...@us.ibm.com > GitHub: github.com/ajbozarth >505 Howard Street > San Francisco, CA 94105 > United States > > > > > -- Marcelo
Re: Missing board report
@marcelo and @jerry you've been reviewing and merging the most recent code changes as I've been a bit too busy. I know we've added a thrift server in the last quarter, could one of you fill out the report this time? If I don't hear back by end of work day then I'll just fill it out to the best of my understanding. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Justin Mclean To: Date: 10/02/2018 01:54 PM Subject:Re: Missing board report HI, Just a reminder that the report is due today and I don't see any discussion on it. It helps me finish the IPMC report on time if you get your report in on time. Thanks, Justin
Re: [DISCUSS] Getting rid of old stuff
I agree with all of Marcelo's points. The last time we discussed this was when Spark 2.2 was new and it was decided that it was probably too soon, but that was awhile ago now. I've been in support of deprecating and removing support for older versions of Java/Scala/Spark for a while and I believe it will allow us to clean up and unify large portions of our code. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States From: Marcelo Vanzin To: dev@livy.incubator.apache.org Date: 09/13/2018 03:10 PM Subject:[DISCUSS] Getting rid of old stuff Hey all, I'd like to gauge people's reaction to some proposals regarding what is supported in Livy. #1: Java versions I propose dropping support for Java 7. Even J8 is already EOL, although it's pretty obvious nobody is getting rid of it anytime soon. But I don't see a good reason to support J7. Even testing it is a nuisance, since most people only have jdk8 around... #2: Spark versions I think we should drop 1.6. At least. This would clean up some code that currently uses reflection, and fix some parts of the API (like the JobContext method to retrieve a "SparkSession" instance). Changing the API is well, not backwards compatible, but I think it's better to do that sort of cleanup earlier than later when the project is more mature. Separately, we could consider dropping 2.0 and 2.1 also. There was talk in the Spark list about making 2.1 EOL - I don't remember a final verdict, but I don't imagine there will be a lot of new deployments of 2.1 going forward, since the only reason to use it is if you're stuck with J7. #3: Scala versions If we decide to only support Spark 2.2+, then the decision is easy. But if we drop 1.6, we should consider dropping Scala 2.10 support. Spark does not ship official builds with 2.10 support in the 2.x line, and it was dropped altogether in 2.2. We shouldn't remove support for multiple versions of Scala, though, since 2.12 will be beta in Spark 2.4, and there will be a 2.13 at some point. Thoughts? -- Marcelo
Re: Podling Report Reminder - July 2018
Given I've been less active this quarter would someone else like to make this quarter's report? If not, I can tackle it agian. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies E-mail: ajboz...@us.ibm.com GitHub: https://github.com/ajbozarth -jmcl...@apache.org wrote: - To: dev@livy.incubator.apache.org From: jmcl...@apache.org Date: 06/27/2018 02:41PM Subject: Podling Report Reminder - July 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, 18 July 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, July 04). 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/July2018 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
[ANNOUNCE] Apache Livy 0.5.0-incubating released
The Apache Livy team is proud to announce the release of Apache Livy 0.5.0-incubating 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. Download Apache Livy 0.5.0-incubating: http://livy.incubator.apache.org/download/ Release Notes: http://livy.incubator.apache.org/history/ For more about Livy check our website: http://livy.incubator.apache.org/ On behalf of your Apache Livy team, 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
[RESULTS] [VOTE] Release Apache Livy 0.5.0-incubating (RC2)
This vote has passed with three +1 binding votes and no -1s or 0s. +1 (binding): Justin Mclean Luciano Resende Jean-Baptiste Onofré (carried over from the Livy dev vote) Thank you to those that voted, I will follow up with the release and announcement at the start of next week. 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 From: "Alex Bozarth" <ajboz...@us.ibm.com> To: gene...@incubator.apache.org Cc: dev@livy.incubator.apache.org Date: 01/29/2018 08:56 PM Subject:[VOTE] Release Apache Livy 0.5.0-incubating (RC2) The Apache Livy community has voted on and approved a proposal to release Apache Livy 0.5.0-incubating (RC2). We would like to request that the Incubator PMC members review and vote on this incubator release candidate. Apache Livy (incubating) 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. The livy dev voting thread can be found here: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mail-2Darchive.com_dev-40livy.incubator.apache.org_msg00297.html=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=KMyzqbWH-_wvXigmaGS87yHcYzpZNbJiY8bTu_mzt88=A4Zj9gq_lY03yGNaX1_vdv2qhHnUGV4L977gCZNZ9SI= And the results here: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.mail-2Darchive.com_dev-40livy.incubator.apache.org_msg00308.html=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=KMyzqbWH-_wvXigmaGS87yHcYzpZNbJiY8bTu_mzt88=bkZOidHCkYJLm_b8zKiBTgmrMwPVokBfx1RwY81U4po= Git tag: v0.5.0-incubating-rc2 https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Dlivy_tree_v0.5.0-2Dincubating-2Drc2=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=KMyzqbWH-_wvXigmaGS87yHcYzpZNbJiY8bTu_mzt88=O_kxYpiepl0wVaKyaz8eCsYl-MH4tUR33TVpv3FPjuY= All distribution packages, including signatures, digests, etc. can be found at: https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_livy_=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=KMyzqbWH-_wvXigmaGS87yHcYzpZNbJiY8bTu_mzt88=p94R0sDvo-3IQsQ7K6hCpkyQw-7I-jDjFkBnnzT2O7o= Staging artifacts can be found at: https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache.org_content_repositories_orgapachelivy-2D1005_=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=KMyzqbWH-_wvXigmaGS87yHcYzpZNbJiY8bTu_mzt88=io8fHD48IMg_fp25H7oJMG29WbUK012gQ-U9F5oB-bQ= The vote is open for at least 72 hours and passes if a majority of at least 3 +1 PMC votes are cast. [ ] +1 Release this package as Apache Livy 0.5.0-incubating [ ] -1 Do not release this package because ... Thank you on behalf of the Apache Livy community, 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: Podling Report Reminder - February 2018
As I mentioned earlier this month I will take care of this, but I plan to wait until the results of the PMC vote on 0.5 so as to include that in our update. 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 From: johndam...@apache.org To: dev@livy.incubator.apache.org Date: 01/29/2018 08:20 PM Subject:Podling Report Reminder - February 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, 21 February 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, February 07). 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. 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://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.apache.org_incubator_February2018=DwICAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=YmrTieC32JU6kAWV9zcZcEDMweskGvYUeHEH945J-gg=QL2AZY2YrPNqDFF9S-MHVuyUYSBD48iCNMofSmAUhHw= 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
[VOTE] Release Apache Livy 0.5.0-incubating (RC2)
The Apache Livy community has voted on and approved a proposal to release Apache Livy 0.5.0-incubating (RC2). We would like to request that the Incubator PMC members review and vote on this incubator release candidate. Apache Livy (incubating) 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. The livy dev voting thread can be found here: https://www.mail-archive.com/dev@livy.incubator.apache.org/msg00297.html And the results here: https://www.mail-archive.com/dev@livy.incubator.apache.org/msg00308.html Git tag: v0.5.0-incubating-rc2 https://github.com/apache/incubator-livy/tree/v0.5.0-incubating-rc2 All distribution packages, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/livy/ Staging artifacts can be found at: https://repository.apache.org/content/repositories/orgapachelivy-1005/ The vote is open for at least 72 hours and passes if a majority of at least 3 +1 PMC votes are cast. [ ] +1 Release this package as Apache Livy 0.5.0-incubating [ ] -1 Do not release this package because ... Thank you on behalf of the Apache Livy community, 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: [VOTE] Livy 0.5.0-incubating (RC2)
I've noticed some flaky tests now and then both locally and on travis. I agree that we should delay this release for them, but would you open (or find) a JIRA for the flaky tests so we can address them in the next version? 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 From: Marcelo Vanzin <van...@cloudera.com> To: dev@livy.incubator.apache.org Date: 01/29/2018 05:21 PM Subject:Re: [VOTE] Livy 0.5.0-incubating (RC2) I'm a -0 on this. The signatures check and things seem to compile, but I can't get unit tests to pass. The default profile (spark 1.6) breaks with jacoco errors for me. The spark 2.2 profile is a bit better; but I still run into what look like flaky tests (TestSparkClient fails sometimes, also SessionHeartbeatSpec). I don't want to block the release because of those, since maybe it's something in my environment (haven't really kept up with the requirements), but it sounds a little odd for unit tests to fail in the default profile. On Thu, Jan 25, 2018 at 3:57 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__incubator.apache.org_policy_incubation.html-23releases=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=QGCNTKGdpfian8a4w5n8z3dxmFlE0NOwtsl9_pppw4c=S72UE3fU6JEKil3SPyZ5slSSFKnfF8Z7-Vgfn2k5UIQ= > > This release files can be found here: > https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_livy_0.5.0-2Dincubating-2Drc2_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=QGCNTKGdpfian8a4w5n8z3dxmFlE0NOwtsl9_pppw4c=hw15KIMqzFDt9pcvxxtQbOhpkiRSVqzvDVrRfg6eFvc= > > The list of resolved JIRAs in this release can be found here: > https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_projects_LIVY_versions_12341543=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=QGCNTKGdpfian8a4w5n8z3dxmFlE0NOwtsl9_pppw4c=O7Aws8asSF_YbiRAmXTUmmPgbnb_XTL3QlkIqBRfDEA= > > > 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 > > > > > -- Marcelo
Re: [VOTE] Livy 0.5.0-incubating (RC2)
@Jerry, I was under the impression that I wasn't supposed to run the publish-release portion of your script until the vote passed. Did I misunderstand it, should I run it now? 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 01/25/2018 09:52 PM Subject:Re: [VOTE] Livy 0.5.0-incubating (RC2) asc, sha512 and md5 LGTM. Also checked the package, seems everything is landed. Alex, did you also publish Livy artifacts to staging repo? 2018-01-26 8:03 GMT+08:00 Alex Bozarth <ajboz...@us.ibm.com>: > That works for me, voting will be open an extra day for a total of 96 > hours ending on Tuesday January 30th at 12:00AM (UTC) > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=99wFryM7-af3wH1q-ZSyiwRS3f546sbJ0nr1wztPhXU=hczorLCgl5RXfG8OYxyge9xhvrYkvRjL2OPOfdTxJss= > > > > 505 Howard Street > < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D505-2BHoward-2BStreet-2BSan-2BFrancisco-2C-2BCA-2B94105-2BUnited-2BStates-26entry-3Dgmail-26source-3Dg=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=99wFryM7-af3wH1q-ZSyiwRS3f546sbJ0nr1wztPhXU=xpp-A2xQw1IllEgPbN0m62Lv7L2oQmYWPTqWEc3qHCg= > > San Francisco, CA 94105 > < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D505-2BHoward-2BStreet-2BSan-2BFrancisco-2C-2BCA-2B94105-2BUnited-2BStates-26entry-3Dgmail-26source-3Dg=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=99wFryM7-af3wH1q-ZSyiwRS3f546sbJ0nr1wztPhXU=xpp-A2xQw1IllEgPbN0m62Lv7L2oQmYWPTqWEc3qHCg= > > United States > < https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3D505-2BHoward-2BStreet-2BSan-2BFrancisco-2C-2BCA-2B94105-2BUnited-2BStates-26entry-3Dgmail-26source-3Dg=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=99wFryM7-af3wH1q-ZSyiwRS3f546sbJ0nr1wztPhXU=xpp-A2xQw1IllEgPbN0m62Lv7L2oQmYWPTqWEc3qHCg= > > > > > [image: Inactive hide details for Marcelo Vanzin ---01/25/2018 04:00:28 > PM---On Thu, Jan 25, 2018 at 3:57 PM, Alex Bozarth <ajbozart@us]Marcelo > Vanzin ---01/25/2018 04:00:28 PM---On Thu, Jan 25, 2018 at 3:57 PM, Alex > Bozarth <ajboz...@us.ibm.com> wrote: > The vote will be open 7 > > From: Marcelo Vanzin <van...@cloudera.com> > To: dev@livy.incubator.apache.org > Date: 01/25/2018 04:00 PM > Subject: Re: [VOTE] Livy 0.5.0-incubating (RC2) > -- > > > > On Thu, Jan 25, 2018 at 3:57 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > 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. > > That means most of the voting period will be on a weekend. Maybe leave > it open a little longer? > > -- > Marcelo > > > > >
Re: [VOTE] Livy 0.5.0-incubating (RC2)
That works for me, voting will be open an extra day for a total of 96 hours ending on Tuesday January 30th at 12:00AM (UTC) 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 From: Marcelo Vanzin <van...@cloudera.com> To: dev@livy.incubator.apache.org Date: 01/25/2018 04:00 PM Subject:Re: [VOTE] Livy 0.5.0-incubating (RC2) On Thu, Jan 25, 2018 at 3:57 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > 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. That means most of the voting period will be on a weekend. Maybe leave it open a little longer? -- Marcelo
[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: Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability
Wow those urls make that email really difficult to understand. I believe what it says is that the nokogiri version we're setting in the Gemlock file should be updated to 1.8.1 to fix a known vulnerability? If so it need's to be addressed in many Apache incubator websites since that Gemlock was imported from the website repo which was forked from the apache website template repo. I can patch it in the morning (unless you'd like to do it) and we can push it to 0.4.1, 0.5.0 and master. I'll have to cut an rc2 tomorrow also in that case. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 01/23/2018 06:16 PM Subject:Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability Hi Alex, Is it due to your recent changes to add ruby file? Thanks Jerry -- Forwarded message -- From: Greg Stein <gst...@gmail.com> Date: 2018-01-24 6:14 GMT+08:00 Subject: Fwd: [apache/incubator-livy] One of your dependencies may have a security vulnerability To: priv...@livy.incubator.apache.org Cc: priv...@incubator.apache.org, priv...@infra.apache.org, secur...@apache.org Livy PPMC: FYI -- Forwarded message -- From: GitHub <notificati...@github.com> Date: Tue, Jan 23, 2018 at 2:22 PM Subject: [apache/incubator-livy] One of your dependencies may have a security vulnerability To: apache/incubator-livy <incubator-l...@noreply.github.com> Cc: Security alert <security_al...@noreply.github.com> We found a potential security vulnerabilty in one of your dependencies [image: GitHub] < https://urldefense.proofpoint.com/v2/url?u=http-3A__sgmail.githubmail.com_wf_click-3Fupn-3DlYxq-2D2FYU7yocrdKNILYalBlaoUQ7ZnNSfaod-2D2BRPoWgKQ-2D3D-5Fw6S5n3vrKqGS7A36Z0jQnv0H94jgQYM8GX7TqkbHsZJGWdsYqQFjxwriEF8ZmW1sZ8ttXgzgS3BVWKu3VBqXOMpSzW2VEkJKKe2e9uTex9Q7Z9UijIWv0RRYA-2D2Fdc2r546s6eSy8HZocDFla36b4iDH-2D2B3aDT4HLjIh-2D2Fo9vK3qWDuW00SPllrHUyE-2D2F7oUepVlho6xRLLFnygiZnALZqGXTakYwTsw7U1i0kOz8YTJZN0atv-2D2B6Wb8Vsz97NI2noXzGt=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=Nb2s-wD-u11k66Q4U1HKkndVLMmWEk0K2SJ8nMDlxjw=jYMgIvM9_yt_Km6BPb_6bGayAwBnNfdQfyEIUl0nh-c= > Sign in < https://urldefense.proofpoint.com/v2/url?u=http-3A__sgmail.githubmail.com_wf_click-3Fupn-3DlYxq-2D2FYU7yocrdKNILYalBluE-2D2FGrtUQ7WwbM8S6nEaj0-2D3D-5Fw6S5n3vrKqGS7A36Z0jQnv0H94jgQYM8GX7TqkbHsZJGWdsYqQFjxwriEF8ZmW1sJEB6DZ3WcL-2D2F4II6g4nOXtSt18YBqIm8t9ln67kM2qPU7-2D2BwIp1OhBha1A2HxxgKMyX40eU0B-2D2BxCoEbAUvsw0AB0X9T5UGmnA4C-2D2BYrM2D-2D2B3MDuTZhqAqaXY6Ippc5CRnN3usIzrFwtPWH1tKIk-2D2FIapGBC7Y2Lsyw7S4QWTtwqE8U67-2D2FuDGyxs1Fd0tvqdx9gIQ=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=Nb2s-wD-u11k66Q4U1HKkndVLMmWEk0K2SJ8nMDlxjw=K2tkQ2Tb9oa3Sjqjz5vsiIS-P2Hy6DqVhKB9spHTchQ= > *gstein,* We found a potential security vulnerability in a repository for which you have been granted security alert access. [image: @apache] apache/incubator-livy < https://urldefense.proofpoint.com/v2/url?u=http-3A__sgmail.githubmail.com_wf_click-3Fupn-3DlYxq-2D2FYU7yocrdKNILYalBg5kFs28ucWJkBdd8Thfp23Ag8-2D2FxhdvxK9GAMrvp8gUC-5Fw6S5n3vrKqGS7A36Z0jQnv0H94jgQYM8GX7TqkbHsZJGWdsYqQFjxwriEF8ZmW1sqJPyhuVFWI7a-2D2BCvW4tyXVGKVBZY13BEvr-2D2Bq0IaZU-2D2BUr9JXtZ-2D2FwPj4cV2z3v3QVEOiwfg1cPLVN93lsgJ8m5RMCdkFQBaHX-2D2Bxc-2D2B-2D2BIRsFowmpW0QyMBlxuDLaxDM4JwxNhXI3BIM7nyaHpSS-2D2FYq6xcOzCY2u-2D2B-2D2B2GH1SAI3PmsjyEjQqdMIARNgBMpvoIRbrRgp=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=Nb2s-wD-u11k66Q4U1HKkndVLMmWEk0K2SJ8nMDlxjw=TIOzm9vKkovR4wJNqRAwHMl94HpjJEbjDHlA11VNiY0= > Known * critical severity* security vulnerability detected in nokogiri < 1.8.1 defined in Gemfile.loc
[VOTE] Livy 0.5.0-incubating (RC1)
Hey team, RC1 of Livy 0.5.0-incubating is ready for testing and approval. The vote will be open 72 hours until Saturday January 27th at 2: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-rc1/ 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
Thanks Marcelo, I'm on it. Also I opened a JIRA to track the 0.5 release process as well: https://issues.apache.org/jira/browse/LIVY-434 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 From: Marcelo Vanzin <van...@cloudera.com> To: dev@livy.incubator.apache.org Cc: Alex Bozarth <ajboz...@us.ibm.com> Date: 01/16/2018 02:19 PM Subject:Re: 0.5-incubating release timing Just added both of you as admins. Admin away. On Tue, Jan 16, 2018 at 2:17 PM, Bikas Saha <bi...@apache.org> wrote: > 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 <ajboz...@us.ibm.com> > 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 > > > > > -- Marcelo
Re: Looking to contribute
You are correct that we haven't utilized a beginner label in the JIRA yet. I would suggest reading through the open JIRAs (there not that many compared to other projects) and just try some out, that was how I started last year. And don't worry about opening PRs for everything you start, I started working on quite a few before realizing it was too much for a beginner and moving on to another task. 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 From: Avneet Oberoi <dev.avnee...@gmail.com> To: dev@livy.incubator.apache.org Date: 01/09/2018 03:34 PM Subject:Looking to contribute Hello, I'm a newbie and looking to contribute to Livy. While I wait for feedback on https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_LIVY-2D401=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=lp-EoREQVfVgQZDLZoCfWTR9QDjicMNLJYE5Tcsi6ks=ugGesV3vgEsiUD-OU6uvpZ0l_LeLhvIxEieeW0EIdkQ= , I was wondering if there's some more tasks I could take up. I've searched JIRA already, but barely saw any ones tagged with the newbie label, so thought I should ask here. Thanks, Avneet
Re: Can anyone get email about livy jira change
I think he was talking about getting email notifications from the Apache JIRA when someone comments on or changes a Livy JIRA. I looked through my email's trash folder and found that I haven't been getting any email notifications about Livy JIRAs either, only Spark and INFRA. @Jeff: Open an INFRA JIRA to see if there's some setting wrong on the Livy JIRA Project that's stopping email notifications. 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 From: Marcelo Vanzin <van...@cloudera.com> To: dev@livy.incubator.apache.org Date: 09/13/2017 09:17 AM Subject:Re: Can anyone get email about livy jira change Are you subscribed to iss...@livy.incubator.apache.org? I just found out I wasn't, so I'm not sure it's actually working. It's not listed on the web site, so easy to miss. On Wed, Sep 13, 2017 at 2:26 AM, Jeff Zhang <zjf...@gmail.com> wrote: > Hi all, > > I can get email notification about jira changes of other apache projects, > but never receive email about livy ticket. Can anyone get email about livy > jira change ? Or does it need some configuration on the jira system ? -- Marcelo
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
From: Marcelo Vanzin <van...@cloudera.com>
To: dev@livy.incubator.apache.org
Cc: "u...@livy.incubator.apache.org"
<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 <ajboz...@us.ibm.com> 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 <meisam.fa...@gmail.com>
To: "u...@livy.incubator.apache.org" <u...@livy.incubator.apache.org>, "
dev@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
Sounds good to me, I'm working on fleshing out documentation and adding javadocs, but that's more of an improvement than a feature. 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 From: Bikas Saha <bikas.apa...@outlook.com> To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org> Date: 09/07/2017 04:23 PM Subject:Re: [DISCUSS] Release Cadence 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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=K0WPyiqakFHs_xxQvu3rwaJYj-NBi7aMb01KHHV8s3c=8jI9_7qV9Dh7_-rQh_OjK-qcE4cIB7JPRDAwu-5PVSs= > 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-R
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 GitHub: github.com/ajbozarth 505 Howard Street San Francisco, CA 94105 United States 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: 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 From: Saisai Shao <sai.sai.s...@gmail.com> 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 <ajboz...@us.ibm.com> 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* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=hUGxrkJa6yavXNv9UWSQkfuKkU67CuDR_DNeZGEQa7g=9gzRskQ0ysFuc0j7D3T-wCikcW1AR0sCTXoqND7IYn0= > > > > 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 <sai.sai.s...@gmail.com> > 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 <ajboz...@us.ibm.com> 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* <ajboz...@us.ibm.com> > > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=hUGxrkJa6yavXNv9UWSQkfuKkU67CuDR_DNeZGEQa7g=oUMtC2kpv7Q_9MwJtfgMskUp5m_gemA8nugCG_8hm3A= .> proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth= > DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ- > cx37DPYDyo=fMV22rxtZ56xBOsS_08nAtWN0INQGs6rwMRoj1ot8js= > CzCDePcP9HxXc4FCCima2ThJ0zgF6K5oHcRKWJEegMg= > > > > > >
Re: The process of Livy 0.4.0-incubating release
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 From: Saisai Shao <sai.sai.s...@gmail.com> 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 <ajboz...@us.ibm.com> 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* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* < https://urldefense.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 <sai.sai.shao@gmail.c > > From: Jeff Zhang <zjf...@gmail.com> > 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 published. > > Saisai Shao <sai.sai.s...@gmail.com>于2017年8月31日周四 上午8:35写道： > > > Hi Alex, > > > > I think you can update the website PR firstly to link to the correct > > download URL (since the package is already available) and doc. > > > > I'm working on publish jars to nexus repository, currently I'm waiting > for > > infra team to create a Livy nexus profile, so I push push jars to staging > > repo. > > > > Is it OK to announce now? Since we haven't yet pushed jars, technically > the > > release process is not finished. > > > > I will cleanup some unnecessary branches and tags, one thing is that is > it > > OK to remove gh-pages branch? > > > > Thanks > > Jerry > > > > > > > > On Thu, Aug 31, 2017 at 2:59 AM, Alex Bozarth <ajboz...@us.ibm.com> > wrote: > > > > > So is the release ready to announce then? The apache bin/src download > > > links are live so all I need for the website update is an official > > release > > > date, would that be today or the day we announce to the user list? On a > > > related note, should we clean up our branches and tags on the git repo? > > It > > > makes sense to remove the rc tags, but should we also
Re: The process of Livy 0.4.0-incubating release
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 505 Howard Street San Francisco, CA 94105 United States From: Jeff Zhang <zjf...@gmail.com> 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 published. Saisai Shao <sai.sai.s...@gmail.com>于2017年8月31日周四 上午8:35写道： > Hi Alex, > > I think you can update the website PR firstly to link to the correct > download URL (since the package is already available) and doc. > > I'm working on publish jars to nexus repository, currently I'm waiting for > infra team to create a Livy nexus profile, so I push push jars to staging > repo. > > Is it OK to announce now? Since we haven't yet pushed jars, technically the > release process is not finished. > > I will cleanup some unnecessary branches and tags, one thing is that is it > OK to remove gh-pages branch? > > Thanks > Jerry > > > > On Thu, Aug 31, 2017 at 2:59 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > So is the release ready to announce then? The apache bin/src download > > links are live so all I need for the website update is an official > release > > date, would that be today or the day we announce to the user list? On a > > related note, should we clean up our branches and tags on the git repo? > It > > makes sense to remove the rc tags, but should we also get rid of the > extra > > branches other than "branch-0.x" > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center > > -- > > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=zDjACJJqa08AnZmjSeGhW07H5m36H1Jm-wbbwP_BFX8=xlygKgJEYxQqGARDhM7RSr8ZPQEW7fo1xuhNihFXR68= > > > > > > > 505 Howard Street > > San Francisco, CA 94105 > > United States > > > > > > > > [image: Inactive hide details for Saisai Shao ---08/30/2017 12:05:24 > > AM---Looks like I wronged the releasing process, I should publish]Saisai > > Shao ---08/30/2017 12:05:24 AM---Looks like I wronged the releasing > > process, I should publish jars to staging repo according with RC > > > > From: Saisai Shao <sai.sai.s...@gmail.com> > > To: dev@livy.incubator.apache.org > > Date: 08/30/2017 12:05 AM > > Subject: Re: The process of Livy 0.4.0-incubating release > > -- > > > > > > > > Looks like I wronged the releasing process, I should publish jars to > > staging repo according with RC vote, and after vote passed click release > to > > publish jars. But what I currently do is to publish jars to staging repo > > after vote passed. I'm really sorry about not familiar with the process. > I > > will write a doc as well as release script for the next release. > > > > Sorry about it. > > > > Best regards, > > Jerry > > > > On Wed, Aug 30, 2017 at 2:10 PM, Saisai Shao <sai.sai.s...@gmail.com> > > wrote: > > > > > Hi Luciano, > > > > > > I'm trying to push ma
Re: The process of Livy 0.4.0-incubating release
So is the release ready to announce then? The apache bin/src download links are live so all I need for the website update is an official release date, would that be today or the day we announce to the user list? On a related note, should we clean up our branches and tags on the git repo? It makes sense to remove the rc tags, but should we also get rid of the extra branches other than "branch-0.x" 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 08/30/2017 12:05 AM Subject:Re: The process of Livy 0.4.0-incubating release Looks like I wronged the releasing process, I should publish jars to staging repo according with RC vote, and after vote passed click release to publish jars. But what I currently do is to publish jars to staging repo after vote passed. I'm really sorry about not familiar with the process. I will write a doc as well as release script for the next release. Sorry about it. Best regards, Jerry On Wed, Aug 30, 2017 at 2:10 PM, Saisai Shao <sai.sai.s...@gmail.com> wrote: > Hi Luciano, > > I'm trying to push maven artifacts to maven staging repository at > repository.apache.org, seems we need a org.apache.livy staging profile to > use to create a staging repo, I checked Spark release script, it has a > profile "d63f592e7eac0" used to create repo, do we need this profile for > Livy? Also how can I create this profile? > > Thanks > Jerry > > > On Mon, Aug 28, 2017 at 3:39 PM, Luciano Resende <luckbr1...@gmail.com> > wrote: > >> On Sun, Aug 27, 2017 at 11:53 PM, Saisai Shao <sai.sai.s...@gmail.com> >> wrote: >> >> > Hi mentors, >> > >> > Would you please guide us on how to release the Livy 0.4.0-incubating, >> > including artifact publish. >> > >> >> The artifacts move from : >> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_livy_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0=7tRxDlukXRLudKDtlpeeok3lzvCDHHYw-7oMx8fwz-I= >> >> to >> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_release_incubator_livy_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0=fKrHDzEReoqNRDrYzvoBKQ0hN7wHdFsSgJ0ka3vNDJk= >> >> >> > >> > Also regarding push artifacts to repo, are we inclining to change to >> Maven >> > central repo, or we still use Cloudera repo, any suggestion? >> > >> > >> You should have a maven staging repository at repository.apache.org, >> after >> a release is approved, that repository should just be released. >> >> >> > 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? >> > >> > >> +0, I would say do what you have been doing in the past >> >> >> > Thanks for your help and suggestion. >> > >> > Best regards, >> > Saisai (Jerry) >> > >> >> >> >> -- >> Luciano Resende >> https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_lresende1975=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0=ooMsKS7OJms1O05-O2L786_xRXZLHYTvQ1aVPDEy_9s= >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lresende.blogspot.com_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0=IWI3eFgaDV6GPzGVufAJAQioCPr7ydFrZhfYZEKPhvo= >> > >
Re: Update ASF GitHub Bot Settings?
For now I had the disable the Bot until we figure out how to just link to the PRs. The JIRA is still open as I continue to work with INFRA to figure out the cleanest solution. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 08/28/2017 08:06 PM Subject:Re: Update ASF GitHub Bot Settings? I saw Zeppelin also mirror everything from github to JIRA, if INFRA is hard to change to what you expected, I'm fine with current way. Since Livy is not so active as Spark, we may not suffer from reviewing pain. On Tue, Aug 29, 2017 at 10:47 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Spark does use a script to do it, but that script requires a special admin > JIRA account and is run via a cron job as part of the pr dashboard website > by Databricks ( https://urldefense.proofpoint.com/v2/url?u=https-3A__spark-2Dprs.appspot.com=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=SjTt1qE5cspyP3qnoBjc6odEFzLw-bpiDen-wpwbxbY=woNYFDKuCetDj8Lhg1DkrukXuXew9ksmJtSPJ6Y3If0= ). The website source code is > open source and I've actually done quick a bit of work with it, but it > requires a paid Google CloudPlat account to run in production. Overall I > like how Spark does it but it's not as simple to reproduce as it seems. If > someone want to pay for a Google CloudPlat account and set up a ASF JIRA > Bot like Spark's then I can easily set up a LIVY PR Dash that will run the > JIRA update cron job. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=SjTt1qE5cspyP3qnoBjc6odEFzLw-bpiDen-wpwbxbY=bELSTG9kQQGqyAmFifBzuILNSrubbyqUZfC0gk6KYlA= > > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---08/28/2017 06:53:28 > PM---Hi Alex, Do you want to achieve what Spark did in the JIRA? A]Saisai > Shao ---08/28/2017 06:53:28 PM---Hi Alex, Do you want to achieve what Spark > did in the JIRA? AFAIK Spark uses a > > From: Saisai Shao <sai.sai.s...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 08/28/2017 06:53 PM > Subject: Re: Update ASF GitHub Bot Settings? > -- > > > > Hi Alex, > > Do you want to achieve what Spark did in the JIRA? AFAIK Spark uses a > script to sync between github and jira, it doesn't enable gihub robot to > mirror everything from github. > > Thanks > Jerry > > On Tue, Aug 29, 2017 at 5:00 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > Opened an INFRA JIRA https://urldefense.proofpoint.com/v2/url?u=https-3A__urldefense.proofpoint=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=SjTt1qE5cspyP3qnoBjc6odEFzLw-bpiDen-wpwbxbY=Sn_xRmZX9FXGHizoISGSMAu8WzmhUB4dX2YjL7m6Fks= . > com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA- > 2D14973=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_ > S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=HecI9o5Yex3-t- > KdkHKD8f-oItRwZk_z7jkZ9L_Rp9s=aKdBIISGMsMO4cfi6VP9M2s4SNcUCq > 2kpHytTTTjekg= > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center > > -- > > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__urld
Re: Update ASF GitHub Bot Settings?
Spark does use a script to do it, but that script requires a special admin JIRA account and is run via a cron job as part of the pr dashboard website by Databricks (https://spark-prs.appspot.com). The website source code is open source and I've actually done quick a bit of work with it, but it requires a paid Google CloudPlat account to run in production. Overall I like how Spark does it but it's not as simple to reproduce as it seems. If someone want to pay for a Google CloudPlat account and set up a ASF JIRA Bot like Spark's then I can easily set up a LIVY PR Dash that will run the JIRA update cron job. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 08/28/2017 06:53 PM Subject:Re: Update ASF GitHub Bot Settings? Hi Alex, Do you want to achieve what Spark did in the JIRA? AFAIK Spark uses a script to sync between github and jira, it doesn't enable gihub robot to mirror everything from github. Thanks Jerry On Tue, Aug 29, 2017 at 5:00 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Opened an INFRA JIRA https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_INFRA-2D14973=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=HecI9o5Yex3-t-KdkHKD8f-oItRwZk_z7jkZ9L_Rp9s=aKdBIISGMsMO4cfi6VP9M2s4SNcUCq2kpHytTTTjekg= > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=HecI9o5Yex3-t-KdkHKD8f-oItRwZk_z7jkZ9L_Rp9s=l0AeGk6t8q38vabAkHUe5zM4IkEfHujrrL2FROo2WbM= > > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for "Alex Bozarth" ---08/28/2017 12:08:36 > PM---Is there a place where it describes the default and/or the]"Alex > Bozarth" ---08/28/2017 12:08:36 PM---Is there a place where it describes > the default and/or the options that I could use as reference whe > > From: "Alex Bozarth" <ajboz...@us.ibm.com> > To: dev@livy.incubator.apache.org > Date: 08/28/2017 12:08 PM > Subject: Re: Update ASF GitHub Bot Settings? > -- > > > > Is there a place where it describes the default and/or the options that I > could use as reference when filing the JIRA? > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* > < https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ajbozarth=DwMFAg=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=flEt_Q08XzmKdKaGAHO3RTe5JvMKgEVjZKBtN1_TGiA=Ul0Q03YqdRvD21qPYqtc4jejt08ThOzUqaKEiaJlgjE= > > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > Luciano Resende ---08/28/2017 12:06:37 PM---Please file an INFRA jira > describing you want to change the GitHub workflow. On Mon, Aug 28, 2017 at > > From: Luciano Resende <luckbr1...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 08/28/2017 12:06 PM > Subject: Re: Update ASF GitHub Bot Settings? > -- > > > > Please file an INFRA jira describing you want to change the GitHub > workflow. > > On Mon, Aug 28, 2017 at 11:22 AM, Alex Bozarth <ajboz...@us.ibm.com> > wrote: > > > > > > > Is
Re: Update ASF GitHub Bot Settings?
Opened an INFRA JIRA https://issues.apache.org/jira/browse/INFRA-14973
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
From: "Alex Bozarth" <ajboz...@us.ibm.com>
To: dev@livy.incubator.apache.org
Date: 08/28/2017 12:08 PM
Subject:Re: Update ASF GitHub Bot Settings?
Is there a place where it describes the default and/or the options that I
could use as reference when filing the JIRA?
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
Luciano Resende ---08/28/2017 12:06:37 PM---Please file an INFRA jira
describing you want to change the GitHub workflow. On Mon, Aug 28, 2017 at
From: Luciano Resende <luckbr1...@gmail.com>
To: dev@livy.incubator.apache.org
Date: 08/28/2017 12:06 PM
Subject: Re: Update ASF GitHub Bot Settings?
Please file an INFRA jira describing you want to change the GitHub
workflow.
On Mon, Aug 28, 2017 at 11:22 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
>
>
> Is there a way to edit the default ASF GitHub Bot settings? I think it's
> great that it auto-comments on our JIRAs with links to new PRs, but it's
> also auto-commenting on the JIRAs for every single comment on those PRs,
> which clutters up both the JIRA and the Activity Stream (which is how I
> personally keep up on the Livy JIRAs.
>
>
> 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
>
>
>
>
>
>
--
Luciano Resende
https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_lresende1975=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=K1uiNBsM4Wi-52dZ-0QOOhg_AUEd4fcpd9FOpKarXcQ=Hs8Np4fmjmGtSQm-ie9fPs579ISVlLeGjDUtLqyCaI8=
https://urldefense.proofpoint.com/v2/url?u=http-3A__lresende.blogspot.com_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=K1uiNBsM4Wi-52dZ-0QOOhg_AUEd4fcpd9FOpKarXcQ=_-mxqeV83wkvel4Y367vbHlPkKqkEM_xY6R1KfyysoE=
Re: Update ASF GitHub Bot Settings?
Is there a place where it describes the default and/or the options that I could use as reference when filing the JIRA? 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 From: Luciano Resende <luckbr1...@gmail.com> To: dev@livy.incubator.apache.org Date: 08/28/2017 12:06 PM Subject:Re: Update ASF GitHub Bot Settings? Please file an INFRA jira describing you want to change the GitHub workflow. On Mon, Aug 28, 2017 at 11:22 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > Is there a way to edit the default ASF GitHub Bot settings? I think it's > great that it auto-comments on our JIRAs with links to new PRs, but it's > also auto-commenting on the JIRAs for every single comment on those PRs, > which clutters up both the JIRA and the Activity Stream (which is how I > personally keep up on the Livy JIRAs. > > > 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 > > > > > > -- Luciano Resende https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_lresende1975=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=K1uiNBsM4Wi-52dZ-0QOOhg_AUEd4fcpd9FOpKarXcQ=Hs8Np4fmjmGtSQm-ie9fPs579ISVlLeGjDUtLqyCaI8= https://urldefense.proofpoint.com/v2/url?u=http-3A__lresende.blogspot.com_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=K1uiNBsM4Wi-52dZ-0QOOhg_AUEd4fcpd9FOpKarXcQ=_-mxqeV83wkvel4Y367vbHlPkKqkEM_xY6R1KfyysoE=
Update ASF GitHub Bot Settings?
Is there a way to edit the default ASF GitHub Bot settings? I think it's great that it auto-comments on our JIRAs with links to new PRs, but it's also auto-commenting on the JIRAs for every single comment on those PRs, which clutters up both the JIRA and the Activity Stream (which is how I personally keep up on the Livy JIRAs. 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: Help to verify Apache Livy 0.4.0-incubating release
Nice catch, it must not be a big issue though because it's been that way
since the original Livy 0.2.0 release.
@jerry do you think we should update this with a minor and open a rc3 or
just fix it in the next release?
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
From: Meisam Fathi <meisam.fa...@gmail.com>
To: dev@livy.incubator.apache.org
Date: 08/22/2017 10:00 AM
Subject:Re: Help to verify Apache Livy 0.4.0-incubating release
The version of org.apache.httpcomponents:httpclient is different in
/pom.xml from the version in /client-http/pom.xml
/pom.xml ---> ${httpclient.version} ---> 4.5.2
/client-http/pom.xml ---> 4.5.1
Is this intended?
Thanks,
Meisam
On Thu, Aug 17, 2017 at 12:34 AM, Saisai Shao <sai.sai.s...@gmail.com>
> Hi all,
>
>
> We're under progress to make a first Apache release of Livy
>
> (0.4.0-incubating), we really hope you could verify the RC2[1] release
>
> (binary and source) locally and return us the feedbacks.
>
[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_livy_0=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo=Kb-p_IVOP_NdMjLDuaQ3n9M8JuXyOyZoJMW1js8FH1c=LgN1J8mfdzW3GoDhuYQeFGOVag4Ncz_WBKBTcVau970=
.
>
Apache JIRA up and running
Hey team, As of this morning the Livy project is now in the Apache JIRA, so you can now open new issues at: https://issues.apache.org/jira/projects/LIVY A big thanks the Apache INFRA team, specifically Gavin, for getting the import finished for us. Note: All JIRA relations, parent and sub-tasks relations, web links, and attachments were lost in the import. I have addressed this manually for all currently open tasks, adding attachments and links back and linking parent and sub-task JIRAs with a "Child-Issue" JIRA relation. For more information on the import process you can look at the INFRA tracking JIRA: https://issues.apache.org/jira/browse/INFRA-14469 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: New Livy Logo Discussion and Input
No one has given feedback on the idea of a new Livy logo. Is everyone busy, ambivalent, have no ideas, or don't want to change? I can move forward on my own idea, but would love feedback first. 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 From: "Alex Bozarth" <ajboz...@us.ibm.com> To: dev@livy.incubator.apache.org Date: 07/25/2017 02:48 PM Subject:New Livy Logo Discussion and Input Hey Team, With our move to Apache I think we should take time to create a new logo for the project. Our current logo can be seen in the header of the website currently and personally I think we can do better. I have a designer available to help with this but need opinions and feedback from more people than just myself. Any ideas for a logo, from a theme or icon to use, color scheme, name to icon placement is appreciated. Some of the vague concepts I've thought of so far include the idea of a gateway or bridge to symbolize what Livy does. The idea I ran the most with though take the word word Livy itself as the base, Livy is a Latin derivative of Olive so I was looking at olives/olive leaves as an icon and the color olive as a color scheme, which can already been seen on the website. I've also considered leaving in the Spark orange is some capacity. Any amount of input is helpful, I don't want to end up limiting ideas to just what I've already worked on. 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: To release a first Apache version Livy
Does this mean we're opening a release vote? Or are we planning on having rc1 be QA rc's for livy? (there was some discussion on that on the Spark dev list last release) 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 08/07/2017 02:17 AM Subject:Re: To release a first Apache version Livy Hi Team, Today I cut a RC1 release based on branch-0.4, here is the link ( https://github.com/apache/incubator-livy/releases/tag/v0.4.0-incubating-rc1 and https://dist.apache.org/repos/dist/dev/incubator/livy/), would you please help to test and verify. Thanks a lot and appreciate your help. Best regards, Saisai On Sat, Aug 5, 2017 at 10:44 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Last comment on the INFRA JIRA seemed to indicate that they hit a snag > with the import over a week ago and he never got back to us after. He told > us to keep using the Cloudera JIRA until he successfully completed a test > import then we could re-export for him. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Bikas Saha ---08/04/2017 07:22:50 > PM---Hi, Most of those jiras looked like bug fixes to me. Hence I t]Bikas > Saha ---08/04/2017 07:22:50 PM---Hi, Most of those jiras looked like bug > fixes to me. Hence I thought 0.4 could be a bug fix release. > > From: Bikas Saha <bi...@apache.org> > To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org> > Date: 08/04/2017 07:22 PM > Subject: Re: To release a first Apache version Livy > -- > > > > Hi, > > > Most of those jiras looked like bug fixes to me. Hence I thought 0.4 could > be a bug fix release. But I am ok releasing the current state so users can > gets an Apache release to transition to. > > > Given that its still a new project, a shorter cadence would help make bug > fix releases available. > > > Btw, does anyone know whats holding up the Apache jira process? If not, I > can follow up on that. > > > Bikas > > > From: Saisai Shao <sai.sai.s...@gmail.com> > Sent: Thursday, August 3, 2017 7:31:10 PM > To: dev@livy.incubator.apache.org > Subject: Re: To release a first Apache version Livy > > From my side 0.4 might be a feasible choice to release as for Apache. > Reverting all the features and release 0.3.1 is too time-consuming and not > so necessary. > > On Fri, Aug 4, 2017 at 4:16 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > @Bikas The list of JIRAs fixed in 0.4 is 50 long ( > > https://issues.cloudera.org/issues/?jql=project%20%3D% > > 20LIVY%20AND%20fixVersion%20%3D%200.4) so I'm wondering what you mean by > > not including feature work. Are you suggesting we revert some of the work > > for this release and the re-merge it later, or just that you would've > > preferred it that was released without new features, but are okay with > how > > it is anyway? If you're worried about adding features in the first Apache > > release should we also look at re-releasing 0.3.0 as 0.3.1-incubating or > > back support, personally I think it's not worth it. > > > > As for release cadence, so far we've seemed to shoot for a 6 month > cadence > > (was longer this time
Re: To release a first Apache version Livy
There's two open PRs on the livy repo with a follow-up PR on the website
repo:
https://github.com/apache/incubator-livy/pull/25 <- Web UI Log Page
https://github.com/apache/incubator-livy/pull/26 <- Ability to build Livy
Docs
https://github.com/apache/incubator-livy-website/pull/7 <- Add Livy Docs to
Website (it may actually be better to update this and merge it after the
release)
Once the Log Page PR is merged the basic Web UI is complete, the remaining
UI JIRAs are feature adds and tests that can come in the next release.
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
From: Saisai Shao <sai.sai.s...@gmail.com>
To: dev@livy.incubator.apache.org
Date: 07/31/2017 07:12 PM
Subject:Re: To release a first Apache version Livy
Hi Alex, can you please list the JIRAs for UI related works you want to
merge in 0.4 release?
Thanks
On Sat, Jul 29, 2017 at 7:59 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> After some tweaking and opening of PRs today, I'll change my vote to a +1
> with the inclusion of my currently open PRs.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com>
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for "Alex Bozarth" ---07/28/2017 01:01:16
> PM---I'm a +0 on this, I think we should get in a release soon,]"Alex
> Bozarth" ---07/28/2017 01:01:16 PM---I'm a +0 on this, I think we should
> get in a release soon, but I'm not sure if we should wait until
>
> From: "Alex Bozarth" <ajboz...@us.ibm.com>
> To: dev@livy.incubator.apache.org
> Date: 07/28/2017 01:01 PM
> Subject: Re: To release a first Apache version Livy
> --
>
>
>
> I'm a +0 on this, I think we should get in a release soon, but I'm not
> sure if we should wait until the Web UI and Documentation are finished
> (tracking in *LIVY-87* <https://issues.cloudera.org/browse/LIVY-87> and
> *LIVY-384* <https://issues.cloudera.org/browse/LIVY-384>). If others are
> fine releasing with these feature partially complete then I'll be okay as
> well.
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com>
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> Jeff Zhang ---07/28/2017 01:12:24 AM---+1 for making the first apache
> release. Saisai Shao <sai.sai.s...@gmail.com>于2017年7月28日周五 下午3:42
写道：
>
> From: Jeff Zhang <zjf...@gmail.com>
> To: dev@livy.incubator.apache.org
> Date: 07/28/2017 01:12 AM
> Subject: Re: To release a first Apache version Livy
> --
>
>
>
> +1 for making the first apache release.
>
>
> Saisai Shao <sai.sai.s...@gmail.com>于2017年7月28日周五 下午3:42写道：
>
> > Hi Team,
> >
> > We have already done most of the migration works to Apache, I think it
> > would be better to have a first Apache release based on the current
code.
> > What do you think?
> >
> > Thanks
> > Saisai
> >
>
>
>
>
>
>
Re: To release a first Apache version Livy
I'm a +0 on this, I think we should get in a release soon, but I'm not sure if we should wait until the Web UI and Documentation are finished (tracking in LIVY-87 and LIVY-384). If others are fine releasing with these feature partially complete then I'll be okay as well. 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 From: Jeff Zhang <zjf...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/28/2017 01:12 AM Subject:Re: To release a first Apache version Livy +1 for making the first apache release. Saisai Shao <sai.sai.s...@gmail.com>于2017年7月28日周五 下午3:42写道： > Hi Team, > > We have already done most of the migration works to Apache, I think it > would be better to have a first Apache release based on the current code. > What do you think? > > Thanks > Saisai >
New Livy Logo Discussion and Input
Hey Team, With our move to Apache I think we should take time to create a new logo for the project. Our current logo can be seen in the header of the website currently and personally I think we can do better. I have a designer available to help with this but need opinions and feedback from more people than just myself. Any ideas for a logo, from a theme or icon to use, color scheme, name to icon placement is appreciated. Some of the vague concepts I've thought of so far include the idea of a gateway or bridge to symbolize what Livy does. The idea I ran the most with though take the word word Livy itself as the base, Livy is a Latin derivative of Olive so I was looking at olives/olive leaves as an icon and the color olive as a color scheme, which can already been seen on the website. I've also considered leaving in the Spark orange is some capacity. Any amount of input is helpful, I don't want to end up limiting ideas to just what I've already worked on. 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
Need input: Location of Livy Documentation
Hey Team Jerry and I have been discussing (on my recent PR) where we should keep the Livy Documentation files as we move them out of the README. My PR originally moved the two Doc files (on the REST and Programmatic APIs) into the livy website repos so we can display them via the website. Jerry proposed that we keep them in the main livy repo like how Spark does it. Personally given we have just two files I think leaving them in the website repo is simplier for us, but I also understand that as the Documentation grows and changes from version to version it would be better to store it in the more regularly updated repo. What are everyone's opinions on where the Docs should be stored? If we decide to store them in the main repo does anyone have pointers on how to simply and cleanly sync them to the website for viewing. You can see my Documenation and README update PRs here: https://github.com/apache/incubator-livy/pull/21 https://github.com/apache/incubator-livy-website/pull/5 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: When Livy JIRA system will be ready?
You can follow the progress on the INFRA JIRA: https://issues.apache.org/jira/browse/INFRA-14469 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/23/2017 11:32 PM Subject:When Livy JIRA system will be ready? Hi team, May I ask when Livy JIRA system in Apache will be ready? Currently most of the transition works are done except JIRA, contributors still need to create JIRAs on cloudera.org (which has very limited permission) and submit code to Apache. Thanks Saisai
Re: Livy website is now live
Dang, can't believe I messed that one up, I'll submit a fix 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 From: Marcelo Vanzin <van...@cloudera.com> To: dev@livy.incubator.apache.org Date: 07/20/2017 01:39 PM Subject:Re: Livy website is now live Sweet! Shouldn't the page say "incubating" though? e.g. http://impala.incubator.apache.org/ On Thu, Jul 20, 2017 at 1:33 PM, Luciano Resende <luckbr1...@gmail.com> wrote: > We are live now: > > http://livy.incubator.apache.org/ > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ -- Marcelo
Re: Livy Slack and the move to Apache
With 3 +1's I'll post the message to the Slack now and will remove the link on the README in my next PR (should be next week, I have other things to finish this week). 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 From: Luciano Resende <luckbr1...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/20/2017 01:10 PM Subject:Re: Livy Slack and the move to Apache +1 for using the project mailing lists. On Wed, Jul 19, 2017 at 7:21 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > With our move to Apache I looked into and discussed with Luciano how we > should handle the Livy Slack that we link to on the README and came to the > following answer: > > I petition we officially abandon the Livy Dev Slack channel and > leave > final messages pointing users to use the email lists. > > I'm not sure this is something we should vote on, but I strongly believe a > solid decision should be made. There is no precedence for Apache projects > to have Slack channels (since the email lists should be used) and very few > even have unofficial Slack channels. If everyone agrees, I plan to remove > the link to the Slack channel in my upcoming README updates PR and we > should leave official statements pointing to the email list on the Slack. > > > 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 > > > > > > -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: Commit style best practices, was Re: incubator-livy-website git commit: Fix bug in merge_livy_pr.py because incubator-livy-website repo has no branch it's name started with "branch-"
+1. I think we've been using close to this format, but with "LIVY-XXX."
instead of "[LIVY-XXX]". I can include a copy of this Contributing section
in my next update to the livy website if we want, I almost added something
similar in my first update, but decided not to since it hadn't been
discussed yet.
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
From: Marcelo Vanzin <van...@cloudera.com>
To: dev@livy.incubator.apache.org
Date: 07/20/2017 01:12 PM
Subject:Re: Commit style best practices, was Re: incubator-livy-website
git commit: Fix bug in merge_livy_pr.py because
incubator-livy-website repo has no branch it's name started
with "branch-"
+1. Bad commit messages are one of my pet peeves. Although I like
periods at the end of sentences.
On Thu, Jul 20, 2017 at 1:09 PM, Luciano Resende <luckbr1...@gmail.com>
wrote:
> Could we try to follow some best practices on PR title, commit message,
etc?
>
> Some info from: http://bahir.apache.org/contributing/#Creating+a+Pull+
> Request
>
> - Open a pull request against the master branch
>
>- The PR title should be of the form [LIVY-] Title, where
LIVY-
>is the relevant JIRA number and Title may be the JIRA’s title or a
more
>specific title describing the PR itself.
>- If the pull request is still a work in progress, and so is not ready
>to be merged, but needs to be pushed to Github to facilitate review,
then
>add [WIP] after the component.
>- For website work, a JIRA is not required
>
> - Follow The 7 rules for a great commit message
> <http://chris.beams.io/posts/git-commit/>
>
>- Separate subject from body with a blank line
>- Limit the subject line to 50 characters
>- Capitalize the subject line
>- Do not end the subject line with a period
>- Use the imperative mood in the subject line
>- Wrap the body at 72 characters
>- Use the body to explain what and why vs. how
>
> Below is an example of a good commit message
>
> [LIVY-001] Performance enhancements for decision tree
>
> Generate Matrix with random values through local memory
> if there is sufficient memory.
>
>
>
> Thoughts ?
>
> On Thu, Jul 20, 2017 at 1:03 PM, <js...@apache.org> wrote:
>
>> Repository: incubator-livy-website
>> Updated Branches:
>> refs/heads/master 27348bab6 -> 572b37b1e
>>
>>
>> Fix bug in merge_livy_pr.py because incubator-livy-website repo has no
>> branch it's name started with "branch-"
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
>> e/repo
>> Commit: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
>> e/commit/572b37b1
>> Tree: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
>> e/tree/572b37b1
>> Diff: http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
>> e/diff/572b37b1
>>
>> Branch: refs/heads/master
>> Commit: 572b37b1efc2a2947272790261b6ba023ec53b74
>> Parents: 27348ba
>> Author: jerryshao <ss...@hortonworks.com>
>> Authored: Thu Jul 20 13:02:23 2017 -0700
>> Committer: jerryshao <ss...@hortonworks.com>
>> Committed: Thu Jul 20 13:03:22 2017 -0700
>>
>> --
>> merge_livy_pr.py | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/incubator-livy-websit
>> e/blo
Re: Another approach for Livy Website
I've opened a PR (https://github.com/apache/incubator-livy-website/pull/1) to address feedback from the INFRA JIRA. Could you guys take a look? 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 From: Luciano Resende <luckbr1...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/19/2017 08:11 PM Subject:Re: Another approach for Livy Website One pub-sub is configured, every time we commit to a "content" branch, the website gets updated. On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Thanks, will there be a straight forward process to it for future updates > or will we have to open a INFRA JIRA each time? > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Luciano Resende ---07/19/2017 08:02:27 > PM---Yes, let me create a INFRA JIRA to publish it. On Wed, Ju]Luciano > Resende ---07/19/2017 08:02:27 PM---Yes, let me create a INFRA JIRA to > publish it. On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth > From: Luciano Resende <luckbr1...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/19/2017 08:02 PM > Subject: Re: Another approach for Livy Website > ------ > > > > Yes, let me create a INFRA JIRA to publish it. > > On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > Thanks Luciano, are there any steps we still need to take for the website > > to actually start showing up at livy.incubating.apache.org? It currently > > throws a 404 and livy.apache.org, which should also work, doesn't even > > exist. > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center > > -- > > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > > > > 505 Howard Street > > San Francisco, CA 94105 > > United States > > > > > > > > [image: Inactive hide details for Luciano Resende ---07/19/2017 06:56:52 > > PM---After my little mistake, a pushing from different local r]Luciano > > Resende ---07/19/2017 06:56:52 PM---After my little mistake, a pushing > from > > different local repositry, things are fixed and it should be > > > > From: Luciano Resende <luckbr1...@gmail.com> > > To: dev@livy.incubator.apache.org > > Date: 07/19/2017 06:56 PM > > Subject: Re: Another approach for Livy Website > > ------ > > > > > > > > > After my little mistake, a pushing from different local repositry, things > > are fixed and it should be ready now: > > > > > https://github.com/apache/incubator-livy-website > > > > > Thanks, Alex and others for the patience getting this ready. > > > > > > On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth <ajboz...@us.ibm.com> > wrote: > > > > > Thanks Jerry, > > > > > > @Luciano if the code looks good to you can you do copy? I'll follow up > by > > > opening a few PRs to move the Docs out of the README into the website > > once > > > you've finished the copy. > > > > > > > > > *Alex Bozarth* > > > Software Engineer >
Re: Another approach for Livy Website
Perfect, on a related note, @everyone once the website is up, should we update livy.io to redirect to livy.incubator.apache.com or shut it down? 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 From: Luciano Resende <luckbr1...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/19/2017 08:11 PM Subject:Re: Another approach for Livy Website One pub-sub is configured, every time we commit to a "content" branch, the website gets updated. On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Thanks, will there be a straight forward process to it for future updates > or will we have to open a INFRA JIRA each time? > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Luciano Resende ---07/19/2017 08:02:27 > PM---Yes, let me create a INFRA JIRA to publish it. On Wed, Ju]Luciano > Resende ---07/19/2017 08:02:27 PM---Yes, let me create a INFRA JIRA to > publish it. On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth > From: Luciano Resende <luckbr1...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/19/2017 08:02 PM > Subject: Re: Another approach for Livy Website > ------ > > > > Yes, let me create a INFRA JIRA to publish it. > > On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > Thanks Luciano, are there any steps we still need to take for the website > > to actually start showing up at livy.incubating.apache.org? It currently > > throws a 404 and livy.apache.org, which should also work, doesn't even > > exist. > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center > > -- > > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > > > > 505 Howard Street > > San Francisco, CA 94105 > > United States > > > > > > > > [image: Inactive hide details for Luciano Resende ---07/19/2017 06:56:52 > > PM---After my little mistake, a pushing from different local r]Luciano > > Resende ---07/19/2017 06:56:52 PM---After my little mistake, a pushing > from > > different local repositry, things are fixed and it should be > > > > From: Luciano Resende <luckbr1...@gmail.com> > > To: dev@livy.incubator.apache.org > > Date: 07/19/2017 06:56 PM > > Subject: Re: Another approach for Livy Website > > ------ > > > > > > > > > After my little mistake, a pushing from different local repositry, things > > are fixed and it should be ready now: > > > > > https://github.com/apache/incubator-livy-website > > > > > Thanks, Alex and others for the patience getting this ready. > > > > > > On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth <ajboz...@us.ibm.com> > wrote: > > > > > Thanks Jerry, > > > > > > @Luciano if the code looks good to you can you do copy? I'll follow up > by > > > opening a few PRs to move the Docs out of the README into the website > > once > > > you've finished the copy. > > > > > > > > > *Alex Bozarth* > > > Software Engineer >
Re: Another approach for Livy Website
Thanks Luciano, are there any steps we still need to take for the website to actually start showing up at livy.incubating.apache.org? It currently throws a 404 and livy.apache.org, which should also work, doesn't even exist. 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 From: Luciano Resende <luckbr1...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/19/2017 06:56 PM Subject:Re: Another approach for Livy Website After my little mistake, a pushing from different local repositry, things are fixed and it should be ready now: https://github.com/apache/incubator-livy-website Thanks, Alex and others for the patience getting this ready. On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Thanks Jerry, > > @Luciano if the code looks good to you can you do copy? I'll follow up by > opening a few PRs to move the Docs out of the README into the website once > you've finished the copy. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---07/19/2017 05:17:12 > PM---Hi Alex, if think the changes are pretty ready, you can creat]Saisai > Shao ---07/19/2017 05:17:12 PM---Hi Alex, if think the changes are pretty > ready, you can create a PR to incubator-livy-website. > > From: Saisai Shao <sai.sai.s...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/19/2017 05:17 PM > Subject: Re: Another approach for Livy Website > -- > > > > Hi Alex, if think the changes are pretty ready, you can create a PR to > incubator-livy-website. > > Thanks > Jerry > > On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > > > I have a personal GitHub repo all ready to go: > > https://github.com/ajbozarth/incubator-livy-website > > > > The master branch is a fork of apache/apache-website-template plus my > > Livy update commit. > > The repo also includes an old-site branch with a copy of the gh-pages > > branch from apache/incubator-livy plus a clean up commit leaving only the > > website code. > > > > @Luciano: I added you as a contributor to my repo so you can do whatever > > you need to copy it to apache/incubator-livy-website > > > > @Everyone please look through my updates commit. There's still more to > > add, but I believe for a first push and initial website it's good. > > > > Things I addressed: > > - Updating the template for the Livy project (instead of the default > > template values) > > - Added the content from livy.io and the GitHub wiki page > > - Various html/css tweaking for my personal sanity > > > > Some future things to address that I didn't tackle in my initial commit: > > - Adding the API Docs and Examples from the README > > - Fine tuning of the Website content for professionalism and accuracy, I > > did my best here but we should continue to clean up the site more > > - New Livy logo. Our Current Logo is not that great moving forward and I > > personally believe we should replace it. On this front I'm working to > pitch > > a new logo here on the dev list soon. > > > > > > *Alex Bozarth* > > Software Engineer > > Spark Technology Center > > -- > > *E-mail:* *ajboz...@us.
Cleaning up the repo branches
When we moved the repo to apache/incubator-livy we copied all the branches from cloudera/livy including a few stale branches. Should we cleanup the repo by deleting the stale branches rel-0.2.0-refresh and revert-237-LIVY-255 as well as gh-page, since it was moved to apache/incubator-livy-website? 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: Another approach for Livy Website
Thanks Jerry, @Luciano if the code looks good to you can you do copy? I'll follow up by opening a few PRs to move the Docs out of the README into the website once you've finished the copy. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/19/2017 05:17 PM Subject:Re: Another approach for Livy Website Hi Alex, if think the changes are pretty ready, you can create a PR to incubator-livy-website. Thanks Jerry On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > I have a personal GitHub repo all ready to go: > https://github.com/ajbozarth/incubator-livy-website > > The master branch is a fork of apache/apache-website-template plus my > Livy update commit. > The repo also includes an old-site branch with a copy of the gh-pages > branch from apache/incubator-livy plus a clean up commit leaving only the > website code. > > @Luciano: I added you as a contributor to my repo so you can do whatever > you need to copy it to apache/incubator-livy-website > > @Everyone please look through my updates commit. There's still more to > add, but I believe for a first push and initial website it's good. > > Things I addressed: > - Updating the template for the Livy project (instead of the default > template values) > - Added the content from livy.io and the GitHub wiki page > - Various html/css tweaking for my personal sanity > > Some future things to address that I didn't tackle in my initial commit: > - Adding the API Docs and Examples from the README > - Fine tuning of the Website content for professionalism and accuracy, I > did my best here but we should continue to clean up the site more > - New Livy logo. Our Current Logo is not that great moving forward and I > personally believe we should replace it. On this front I'm working to pitch > a new logo here on the dev list soon. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for "Alex Bozarth" ---07/17/2017 01:13:44 > PM---If that's the best way then I'll set up a fork with all my]"Alex > Bozarth" ---07/17/2017 01:13:44 PM---If that's the best way then I'll set > up a fork with all my previous suggestions and once my initial > > From: "Alex Bozarth" <ajboz...@us.ibm.com> > To: dev@livy.incubator.apache.org > Date: 07/17/2017 01:13 PM > Subject: Re: Another approach for Livy Website > -- > > > > If that's the best way then I'll set up a fork with all my previous > suggestions and once my initial Livy website code is ready I'll post a link > here for review. > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > Luciano Resende ---07/17/2017 01:07:08 PM---Great Alex, Once you have the > fork ok, please ask us to do a quick review and probably > > From: Luciano Resende <luckbr1...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/17/2017 01:07 PM > Subject: Re: Another approach for Livy Website > -- >
Re: Another approach for Livy Website
So it sound like what we want to do is "fork" apache/apache-website-template into the master branch of apache/incubator-livy-website then also move the gh-pages branch out of apache/incubator-livy into apache/incubator-livy-website as well. Unless there's objection/misunderstanding Luciano, Jerry and I agree on that path forward. After these steps happen I will open PRs to update the template with Livy data (I already have this mostly ready) and, if we want to, can also open a PR to clean up the old site branch so it doesn't include all the old livy code, just the old website code. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/14/2017 10:35 AM Subject:Re: Another approach for Livy Website I think the way Luciano and you mentioned (using template and put old code into another branch) is good for me, this is much easier for maintaining and updating compared to directly editing on html files. We can move on the progress unless someone strongly oppose this way. Thanks Jerry On Fri, Jul 14, 2017 at 10:23 AM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > Just an update so there no duplicate work. I forked the template Luciano > mentioned yesterday and have been slowly updating it and filling it out > with some of the current content. If/Once we decide to use template I > should have a solid initial PR ready that will update it for Livy. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for "Alex Bozarth" ---07/13/2017 02:27:50 > PM---The issue with that though is by using the template we pla]"Alex > Bozarth" ---07/13/2017 02:27:50 PM---The issue with that though is by using > the template we plan to not use the current site code, so imp > > From: "Alex Bozarth" <ajboz...@us.ibm.com> > To: dev@livy.incubator.apache.org > Date: 07/13/2017 02:27 PM > Subject: Re: Another approach for Livy Website > -- > > > > The issue with that though is by using the template we plan to not use the > current site code, so importing it to only completely delete and replace it > doesn't make sense to me. Though if it's not against the Apache guidelines > we could always leave the gh-pages branch in the main repo for prior credit > and start from the template in the website repo. I'm not sure what the > apache guidelines are for branches, we do have a few junk branches in the > repo currently. > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > Saisai Shao ---07/13/2017 02:20:04 PM---Maybe we can apply the original > changes to the master branch and then do the changes based on it to > > From: Saisai Shao <sai.sai.s...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/13/2017 02:20 PM > Subject: Re: Another approach for Livy Website > -- > > > > Maybe we can apply the original changes to the master branch and then do > the changes based on it to just keep the history. > > On Thu, Jul 13, 2017 at 2:12 PM, Alex
Re: Another approach for Livy Website
Just an update so there no duplicate work. I forked the template Luciano
mentioned yesterday and have been slowly updating it and filling it out
with some of the current content. If/Once we decide to use template I
should have a solid initial PR ready that will update it for Livy.
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
From: "Alex Bozarth" <ajboz...@us.ibm.com>
To: dev@livy.incubator.apache.org
Date: 07/13/2017 02:27 PM
Subject:Re: Another approach for Livy Website
The issue with that though is by using the template we plan to not use the
current site code, so importing it to only completely delete and replace it
doesn't make sense to me. Though if it's not against the Apache guidelines
we could always leave the gh-pages branch in the main repo for prior credit
and start from the template in the website repo. I'm not sure what the
apache guidelines are for branches, we do have a few junk branches in the
repo currently.
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
Saisai Shao ---07/13/2017 02:20:04 PM---Maybe we can apply the original
changes to the master branch and then do the changes based on it to
From: Saisai Shao <sai.sai.s...@gmail.com>
To: dev@livy.incubator.apache.org
Date: 07/13/2017 02:20 PM
Subject: Re: Another approach for Livy Website
Maybe we can apply the original changes to the master branch and then do
the changes based on it to just keep the history.
On Thu, Jul 13, 2017 at 2:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote:
> I don't have a problem with it but given commits to branches aren't given
> credit in the master branch I'd say if we went with the template we
should
> just start from scratch and forget the history.
>
> On the note of starting from scratch, I support the idea and am willing
to
> personally take on the task of filling out the template with our current
> content. I've already written down a list of current content from the
> website, wiki, and README that makes sense to put in the webpage and was
> planning on putting in a JIRA once the JIRA migrated but I can share it
> here if desired.
>
>
> *Alex Bozarth*
> Software Engineer
> Spark Technology Center
> --
> *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com>
> *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth>
>
>
> 505 Howard Street
> San Francisco, CA 94105
> United States
>
>
>
> [image: Inactive hide details for Saisai Shao ---07/13/2017 01:57:11
> PM---It's fine for me. Not sure if other guys have additional conc]Saisai
Re: Another approach for Livy Website
The issue with that though is by using the template we plan to not use the current site code, so importing it to only completely delete and replace it doesn't make sense to me. Though if it's not against the Apache guidelines we could always leave the gh-pages branch in the main repo for prior credit and start from the template in the website repo. I'm not sure what the apache guidelines are for branches, we do have a few junk branches in the repo currently. 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 From: Saisai Shao <sai.sai.s...@gmail.com> To: dev@livy.incubator.apache.org Date: 07/13/2017 02:20 PM Subject:Re: Another approach for Livy Website Maybe we can apply the original changes to the master branch and then do the changes based on it to just keep the history. On Thu, Jul 13, 2017 at 2:12 PM, Alex Bozarth <ajboz...@us.ibm.com> wrote: > I don't have a problem with it but given commits to branches aren't given > credit in the master branch I'd say if we went with the template we should > just start from scratch and forget the history. > > On the note of starting from scratch, I support the idea and am willing to > personally take on the task of filling out the template with our current > content. I've already written down a list of current content from the > website, wiki, and README that makes sense to put in the webpage and was > planning on putting in a JIRA once the JIRA migrated but I can share it > here if desired. > > > *Alex Bozarth* > Software Engineer > Spark Technology Center > -- > *E-mail:* *ajboz...@us.ibm.com* <ajboz...@us.ibm.com> > *GitHub: **github.com/ajbozarth* <https://github.com/ajbozarth> > > > 505 Howard Street > San Francisco, CA 94105 > United States > > > > [image: Inactive hide details for Saisai Shao ---07/13/2017 01:57:11 > PM---It's fine for me. Not sure if other guys have additional conc]Saisai > Shao ---07/13/2017 01:57:11 PM---It's fine for me. Not sure if other guys > have additional concern. On Thu, Jul 13, 2017 at 1:52 PM, L > > From: Saisai Shao <sai.sai.s...@gmail.com> > To: dev@livy.incubator.apache.org > Date: 07/13/2017 01:57 PM > Subject: Re: Another approach for Livy Website > -- > > > > It's fine for me. Not sure if other guys have additional concern. > > On Thu, Jul 13, 2017 at 1:52 PM, Luciano Resende <luckbr1...@gmail.com> > wrote: > > > I think we could fork the template repository, and try to push the > current > > Livy website as a branch (e.g. original_website) ? That should resolve > the > > current concerns about history/credits. > > > > On Thu, Jul 13, 2017 at 1:45 PM, Saisai Shao <sai.sai.s...@gmail.com> > > wrote: > > > > > I think this is great. Looking from the previous thread our major > concern > > > is to keep the contribution history/credits, will this break the > > > history/credits? If not I think this probably be better. > > > > > > On Thu, Jul 13, 2017 at 1:33 PM, Luciano Resende <luckbr1...@gmail.com > > > > > wrote: > > > > > > > While looking at the current website, it seems that there are only > > three > > > > pages based on pure HTML content. > > > > > > > > Should we look into actually creating a new website from scratch, > based > > > on > > > > Jekkyl, similar to what a few of the other projects are using (e.g. > > > Spark, > > > > Bahir, SystemML, etc). > > > > > > > > If we choose
