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
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
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
This is great! We have a first release.
I will start a thread on general release cadence.
Bikas
From: Alex Bozarth
Sent: Monday, September 4, 2017 9:43 AM
To: dev@livy.incubator.apache.org
Subject: Re: The process of Livy 0.4.0-incubating