Thanks, Alex, for the pointers. I'm happy to step up as Release Manager for this one.
On Wed, Jun 21, 2023 at 12:00 PM Alex Bozarth <ajboz...@us.ibm.com> wrote: > I apologize I don’t have the bandwidth to help manage the release, but I > can pass on what I remember from the last couple releases I did years ago. > > Livy has a release script that we used for our releases: > https://github.com/apache/incubator-livy/blob/master/dev/release-build.sh > > The script has a usage message when run without parameters but given it > hasn’t been run in a couple years you will most likely want to read through > the script and double check that all the hard-coded values are still > correct. IIRC the script can be dry run, but if you’re being extra careful > you can just run it without your Apache credentials saved in the correct > ENV vars. > > Also, for historical reference, we copied the release script from Apache > Spark. So, you can look up their release docs from around the time when we > first committed the release script and those would generally apply to our > release process (I’m assuming Spark has changed its release process since > then and its current doc would not help) > > > Alex Bozarth > IBM Open Quantum > > > From: larry mccay <lmc...@apache.org> > Date: Monday, June 19, 2023 at 6:37 PM > To: ksu...@zohomail.com.invalid <ksu...@zohomail.com.invalid> > Cc: dev <dev@livy.apache.org>, jbonofre <jbono...@apache.org>, dev < > d...@livy.incubator.apache.org>, ajboza...@apache.org <ajboza...@apache.org > > > Subject: [EXTERNAL] Re: [DISCUSS] Time for the Apache Livy 0.8.0 Release > I gave a ghost +1 based @dacort's review and I will use testing while > testing the RC. > > @Jean-Baptiste Onofré <jbono...@apache.org> - I think we are ready to > start > talking about getting an RC ready. > > Note that I just got a wiki space created with a simple overview page with > some article TODOs at the bottom. > One of those is an article on the release process for contributors. > We should target getting that done as well. > > Do you have experience being a release manager for Livy? > If not, would @ajbozarth be willing to help move it forward? > > On Mon, Jun 12, 2023 at 8:37 PM Sumit Kumar <ksu...@zohomail.com.invalid> > wrote: > > > Just thought to update on the progress. > > https://github.com/apache/incubator-livy/pull/407 is ready to be > > reviewed, I've already received one approval from @dacort, waiting > > for mailto:lmc...@apache.org to have a look too. > > > > > > > > > > > > > > > > ---- On Fri, 09 Jun 2023 21:50:54 -0700 Jean-Baptiste Onofré < > > jbono...@apache.org> wrote --- > > > > > > > > +1, it makes sense to have a milestone target. > > > > I would move forward with a release "as it is" as it would be a good > > message to community. > > > > Regards > > JB > > > > On Wed, May 31, 2023 at 7:09 PM larry mccay <mailto:lmc...@apache.org> > > wrote: > > > > > > I can see this being very helpful in the testing of the RC, if we can > > get > > > it in. > > > Even if it is only a partial usecase to test that we can document as > > part > > > of the RC announcement that would give new testers something to > > immediately > > > standup and test. > > > That said, I would timebox this so that we can turn the crank and get > > the > > > release machinery working again within the next week or so. > > > > > > Thoughts? > > > > > > On Tue, May 30, 2023 at 7:37 PM Sumit Kumar <mailto:ksu...@apache.org> > > wrote: > > > > > > > https://issues.apache.org/jira/browse/LIVY-969 aims to make > developer > > > > productivity better by making it easier to develop and test locally > in > > an > > > > integrated environment using docker and docker-compose. May be not > > everyone > > > > would benefit from this immediately if they are not comfortable with > > docker > > > > ecosystem. I'm in favor of making progress, so may be we shouldn't > > block > > > > just for this? How about we cut an RC and see how things go? If I'm > > able to > > > > catch up the train, great; if not, we will march ahead without it? > > > > > > > > > > > > > > > > > > > > > > > > ---- On Tue, 30 May 2023 16:25:35 -0700 larry mccay <mailto: > > larry.mc...@gmail.com> > > > > wrote --- > > > > > > > > > > > > > > > > Is this a release blocker for 0.8.0, @Sumit Kumar <mailto: > > > > mailto:ksu...@apache.org><mailto:ksu...@apache.org%3e> ? > > > > > > > > On Tue, May 30, 2023 at 12:34 PM Sumit Kumar <mailto:mailto: > > ksu...@apache.org> > > > > wrote: > > > > > > > > > I was able to complete the dependency task LIVY-593 but I'm yet to > > make > > > > > progress on LIVY-969, this may take another week or two. > > > > > > > > > > > > > > > > > > > > ---- On Tue, 30 May 2023 08:07:00 -0700 *larry mccay > > > > > <mailto:mailto:larry.mc...@gmail.com <mailto:mailto: > > larry.mc...@gmail.com>>* wrote > > > > --- > > > > > > > > > > Hi @Jean-Baptiste Onofré <mailto:mailto:jbono...@apache.org> - > > > > > > > > > > Thanks for the response! > > > > > I believe that @Sumit Kumar <mailto:mailto:ksu...@apache.org> > spoke > > up and is > > > > asking to > > > > > wait for an PR to be included LIVY-969. > > > > > We should check on the status of that first. > > > > > > > > > > @Sumit Kumar <mailto:mailto:ksu...@apache.org> ? > > > > > > > > > > > > > > > On Mon, May 29, 2023 at 1:59 AM Jean-Baptiste Onofré <mailto: > > > > mailto:j...@nanthrax.net><mailto:j...@nanthrax.net%3e> > > > > > wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > yes, I think it's good time to prepare a new Livy release, it > > would be > > > > > > also a great message to the community. > > > > > > > > > > > > I can do a pass and prepare it. > > > > > > > > > > > > Regards > > > > > > JB > > > > > > > > > > > > On Wed, May 10, 2023 at 2:47 PM larry mccay <mailto:mailto: > > lmc...@apache.org> > > > > wrote: > > > > > > > > > > > > > > All - > > > > > > > > > > > > > > I've noted that the majority of the open JIRA items for 0.8.0 > > have > > > > > been > > > > > > > resolved. > > > > > > > There are a couple that I have moved out to 0.9.0 and a couple > > still > > > > > > > waiting for responses that may be moved out unless they are > > > > considered > > > > > > > blockers. > > > > > > > > > > > > > > At this point, we are looking ~35 total JIRAs in this release: > > > > > > > Full List: > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/LIVY-975?jql=project%20%3D%20LIVY%20AND%20fixVersion%20%3D%200.8.0 > > > > > > > > > > > > > > With a handful of process and doc related items remaining: > > > > > > > > > > > > > > Remaining: > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/LIVY-969?jql=project%20%3D%20LIVY%20AND%20fixVersion%20%3D%200.8.0%20AND%20status%20in%20(Open%2C%20Reopened) > > > > > > > > > > > > > > > > > > > We've addressed a number of dependency CVEs but have a ways to > > go to > > > > > get > > > > > > > rid of all of the Critical and High severity items. This will > > need > > > > to > > > > > > > continue into 0.9.0 and beyond (as they just keep on coming). > > > > > > > > > > > > > > I'd like to target getting a release candidate for 0.8.0 by the > > end > > > > of > > > > > > next > > > > > > > week. > > > > > > > If someone would like to step up as Release Manager for this > > release > > > > > > please > > > > > > > feel free to say so. > > > > > > > > > > > > > > Thoughts, concerns(, jokes)? > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > > > --larry > > > > > > > > > > > > > > > > > > > > > > > > > > >