Great, thank you.
On Mon, Apr 17, 2017 at 12:59 PM, Chip Senkbeil
wrote:
> I just changed everything to use toree again. >_>
>
> https://pypi.python.org/pypi?:action=display&name=toree&version=0.1.0
>
> I can delete this and undo all of it so we can use apache-toree if that's
> what you'd rather
I just changed everything to use toree again. >_>
https://pypi.python.org/pypi?:action=display&name=toree&version=0.1.0
I can delete this and undo all of it so we can use apache-toree if that's
what you'd rather do.
On Mon, Apr 17, 2017 at 2:24 PM Luciano Resende
wrote:
> Just to clarify, we a
Just to clarify, we are going to upload:
https://dist.apache.org/repos/dist/release/incubator/toree/0.1.0-incubating/toree-pip/
I don't have strong opinions for the name, "apache-toree" is even better
than just toree... but we will need to update docs and other stuff, right ?
On Mon, Apr 17, 201
It looks like all of our makefile work was updated awhile ago to use
apache-toree. This must have been from an earlier conversation. I can
update our release artifacts for pip to use toree, but we'll have to go
through the makefile and update it to produce toree in the future if that's
the route we
I looked into some other Apache projects, I believe we could follow the
same pattern and use "toree". but describe it as "Apache Toree
(incubating)". in the description field.
On Mon, Apr 17, 2017 at 9:50 AM, Chip Senkbeil
wrote:
> What is the exact name that you want for the release?
>
> Previo
What is the exact name that you want for the release?
Previously, we were using just "toree", but do you want "apache-toree" or
"apache-toree-incubating"?
On Mon, Apr 17, 2017 at 10:47 AM Luciano Resende
wrote:
> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil
> wrote:
>
>> I've gotten mixed me
On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil
wrote:
> I've gotten mixed messages regarding where the pip artifacts should go.
> Originally, we were going to publish them on https://pypi.python.org/pypi
> (which
> we were previously doing for dev snapshots), but there has been some issues
> wit
I've gotten mixed messages regarding where the pip artifacts should go.
Originally, we were going to publish them on
https://pypi.python.org/pypi (which
we were previously doing for dev snapshots), but there has been some issues
with hosting externally from Apache? Is that still the case? Can we ho
