Perfect, on a related note,
@everyone once the website is up, should we update livy.io to redirect to
livy.incubator.apache.com or shut it down?
Alex Bozarth
One pub-sub is configured, every time we commit to a "content" branch, the
website gets updated.
On Wed, Jul 19, 2017 at 8:08 PM, Alex Bozarth wrote:
> Thanks, will there be a straight forward process to it for future updates
> or will we have to open a INFRA JIRA each time?
>
>
> *Alex Bozarth*
Thanks, will there be a straight forward process to it for future updates
or will we have to open a INFRA JIRA each time?
Alex Bozarth
Soft
Yes, let me create a INFRA JIRA to publish it.
On Wed, Jul 19, 2017 at 7:59 PM, Alex Bozarth wrote:
> Thanks Luciano, are there any steps we still need to take for the website
> to actually start showing up at livy.incubating.apache.org? It currently
> throws a 404 and livy.apache.org, which sho
Thanks Luciano, are there any steps we still need to take for the website
to actually start showing up at livy.incubating.apache.org? It currently
throws a 404 and livy.apache.org, which should also work, doesn't even
exist.
+1 for this.
On Wed, Jul 19, 2017 at 7:30 PM, Jeff Zhang wrote:
> +1 for using apache user mail list.
>
>
>
> Alex Bozarth 于2017年7月20日周四 上午10:21写道：
>
> >
> >
> > With our move to Apache I looked into and discussed with Luciano how we
> > should handle the Livy Slack that we link to on the README
+1 for using apache user mail list.
Alex Bozarth 于2017年7月20日周四 上午10:21写道：
>
>
> With our move to Apache I looked into and discussed with Luciano how we
> should handle the Livy Slack that we link to on the README and came to the
> following answer:
>
> I petition we officially abandon t
When we moved the repo to apache/incubator-livy we copied all the branches
from cloudera/livy including a few stale branches.
Should we cleanup the repo by deleting the stale branches rel-0.2.0-refresh
and revert-237-LIVY-255 as well as gh-page, since it was moved to
apache/incubator-livy-websit
With our move to Apache I looked into and discussed with Luciano how we
should handle the Livy Slack that we link to on the README and came to the
following answer:
I petition we officially abandon the Livy Dev Slack channel and leave
final messages pointing users to use the email lists.
All seems to be resolved now:
https://github.com/apache/incubator-livy-website
On Wed, Jul 19, 2017 at 6:38 PM, Luciano Resende
wrote:
> I did a little mistake while pushing the website, will fix it soon.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
After my little mistake, a pushing from different local repositry, things
are fixed and it should be ready now:
https://github.com/apache/incubator-livy-website
Thanks, Alex and others for the patience getting this ready.
On Wed, Jul 19, 2017 at 5:20 PM, Alex Bozarth wrote:
> Thanks Jerry,
>
I did a little mistake while pushing the website, will fix it soon.
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Thanks Jerry,
@Luciano if the code looks good to you can you do copy? I'll follow up by
opening a few PRs to move the Docs out of the README into the website once
you've finished the copy.
Alex Bozarth
Hi Alex, if think the changes are pretty ready, you can create a PR to
incubator-livy-website.
Thanks
Jerry
On Mon, Jul 17, 2017 at 6:12 PM, Alex Bozarth wrote:
> I have a personal GitHub repo all ready to go:
> https://github.com/ajbozarth/incubator-livy-website
>
> The master branch is a for
14 matches
Mail list logo
