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 want to go.
On Mon, Apr 17, 2017 at 1:27 PM Luciano Resende <luckbr1...@gmail.com> wrote: > 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 <chip.senkb...@gmail.com> > wrote: > >> 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 <luckbr1...@gmail.com> >> wrote: >> >>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <chip.senkb...@gmail.com> >>> 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 with hosting externally from >>>> Apache? Is that still the case? Can we host official releases on Pypi? >>>> >>> >>> Official releases are ok to go there. >>> >>> >>> >>>> If not, we can just indicate that they install via `pip install >>>> https://dist.apache.org/repos/dist/release/incubator/toree/0.1.0-incubating/toree-pip/apache-toree-0.1.0.tar.gz` >>>> or whatever the command is that Gino was mentioning. >>>> >>>> If we want and are allowed to publish on Pypi, I'll do that soon. Just >>>> let me know. >>>> >>>> >>> Yes, please. >>> >>> -- >>> Luciano Resende >>> http://twitter.com/lresende1975 >>> http://lresende.blogspot.com/ >>> >> > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
