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_&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0&s=7tRxDlukXRLudKDtlpeeok3lzvCDHHYw-7oMx8fwz-I&e=
>>
>> to
>>
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_release_incubator_livy_&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0&s=fKrHDzEReoqNRDrYzvoBKQ0hN7wHdFsSgJ0ka3vNDJk&e=
>>
>>
>> >
>> > 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&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0&s=ooMsKS7OJms1O05-O2L786_xRXZLHYTvQ1aVPDEy_9s&e=
>>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lresende.blogspot.com_&d=DwIBaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=S1_S7Dymu4ZL6g7L21O78VQZ53vEnAyZ-cx37DPYDyo&m=73AoTw0B3DG5OXNjZxX9MzTFe42Dx59uljW55vuT2R0&s=IWI3eFgaDV6GPzGVufAJAQioCPr7ydFrZhfYZEKPhvo&e=
>>
>
>
