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
I think we'd better to announce after the artifacts are published.
Saisai Shao 于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
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.
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
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
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