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 with the move to Apache) but I'd be fine moving to > a > > 4 month cadence. I also prefer a time based release. > > > > > > *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/03/2017 12:56:59 > > PM---Hi, My preference would have been to not do a feature bearing]Bikas > > Saha ---08/03/2017 12:56:59 PM---Hi, My preference would have been to not > > do a feature bearing first release so that users could safe > > > > From: Bikas Saha <bi...@apache.org> > > To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org> > > Date: 08/03/2017 12:56 PM > > Subject: Re: To release a first Apache version Livy > > ------------------------------ > > > > > > > > Hi, > > > > > > My preference would have been to not do a feature bearing first release > so > > that users could safely and painlessly migrate to the Apache release. > > Adding features increases the risk of regressions etc. > > > > > > However it seems like the web UI would be a relatively independent > feature > > that would not affect the core stability. So it may be fine to include > that > > in the first release as a new feature. In some ways, it gives users an > > incentive to move to the Apache release. > > > > > > +1 for getting the first release out as soon as feasible. And doing core > > feature work in follow up release. > > > > > > On this note, it would be good to consider the question of release > > cadence. Should we move to a 3 month or 4 month release cadence such that > > release trains are available for features to out when the features are > > ready. Or should do feature releases such that releases come out when > major > > new functionality has added. My preference is a time based release > cadence > > because it provides regular bug and security related fixes available in a > > released form for end users. > > > > > > Thanks! > > > > Bikas > > > > > > ________________________________ > > From: Saisai Shao <sai.sai.s...@gmail.com> > > Sent: Monday, July 31, 2017 8:34:03 PM > > To: dev@livy.incubator.apache.org > > Subject: Re: To release a first Apache version Livy > > > > OK, thanks! Let's get this merged then prepare to the first Apache > release. > > > > On Tue, Aug 1, 2017 at 11:30 AM, Alex Bozarth <ajboz...@us.ibm.com> > wrote: > > > > > 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* <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/31/2017 07:12:11 > > > PM---Hi Alex, can you please list the JIRAs for UI related works > y]Saisai > > > Shao ---07/31/2017 07:12:11 PM---Hi Alex, can you please list the JIRAs > > for > > > UI related works you want to merge in 0.4 release? > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
