You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@toree.apache.org by Luciano Resende <lu...@gmail.com> on 2017/04/16 19:28:58 UTC
Uploading PIP for 0.1.0 release
Hi Chip,
Could you please handle the upload of the PIP install artifacts and
document how to handle that for next releases.
After that, I think we can send the announce e-mail.
Thanks
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Uploading PIP for 0.1.0 release
Posted by Hitesh Shah <hi...@apache.org>.
Either the name or the version should have incubating in it. In most cases,
most projects usually use incubating in the version to keep the name the
same after graduation.
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
Copying Airflow would not be ideal.
-- Hitesh
On Wed, Apr 19, 2017 at 4:39 PM, Marius van Niekerk <
marius.v.niekerk@gmail.com> wrote:
> Airflow doesn't, and they are still incubating
>
> -Marius
>
> On Wed, Apr 19, 2017, 18:27 Hitesh Shah <hi...@apache.org> wrote:
>
> > I believe the version should have "incubating" within it.
> >
> > -- Hitesh
> >
> > On Mon, Apr 17, 2017 at 1:30 PM, Luciano Resende <lu...@gmail.com>
> > wrote:
> >
> > > Great, thank you.
> > >
> > > On Mon, Apr 17, 2017 at 12:59 PM, Chip Senkbeil <
> chip.senkbeil@gmail.com
> > >
> > > 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 do.
> > > >
> > > > On Mon, Apr 17, 2017 at 2:24 PM Luciano Resende <
> luckbr1975@gmail.com>
> > > > wrote:
> > > >
> > > >> 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, 2017 at 11:57 AM, Chip Senkbeil <
> > > chip.senkbeil@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> 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 <
> > luckbr1975@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.senkbeil@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 <
> > > luckbr1975@gmail.com>
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <
> > > >>>>>> chip.senkbeil@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/
> > > >>>>
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >> Luciano Resende
> > > >> http://twitter.com/lresende1975
> > > >> http://lresende.blogspot.com/
> > > >>
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
> --
> regards
> Marius van Niekerk
>
Re: Uploading PIP for 0.1.0 release
Posted by Marius van Niekerk <ma...@gmail.com>.
Airflow doesn't, and they are still incubating
-Marius
On Wed, Apr 19, 2017, 18:27 Hitesh Shah <hi...@apache.org> wrote:
> I believe the version should have "incubating" within it.
>
> -- Hitesh
>
> On Mon, Apr 17, 2017 at 1:30 PM, Luciano Resende <lu...@gmail.com>
> wrote:
>
> > Great, thank you.
> >
> > On Mon, Apr 17, 2017 at 12:59 PM, Chip Senkbeil <chip.senkbeil@gmail.com
> >
> > 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 do.
> > >
> > > On Mon, Apr 17, 2017 at 2:24 PM Luciano Resende <lu...@gmail.com>
> > > wrote:
> > >
> > >> 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, 2017 at 11:57 AM, Chip Senkbeil <
> > chip.senkbeil@gmail.com>
> > >> wrote:
> > >>
> > >>> 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 <
> luckbr1975@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.senkbeil@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 <
> > luckbr1975@gmail.com>
> > >>>>> wrote:
> > >>>>>
> > >>>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <
> > >>>>>> chip.senkbeil@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/
> > >>>>
> > >>>
> > >>
> > >>
> > >> --
> > >> Luciano Resende
> > >> http://twitter.com/lresende1975
> > >> http://lresende.blogspot.com/
> > >>
> > >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>
--
regards
Marius van Niekerk
Re: Uploading PIP for 0.1.0 release
Posted by Hitesh Shah <hi...@apache.org>.
I believe the version should have "incubating" within it.
-- Hitesh
On Mon, Apr 17, 2017 at 1:30 PM, Luciano Resende <lu...@gmail.com>
wrote:
> Great, thank you.
>
> On Mon, Apr 17, 2017 at 12:59 PM, Chip Senkbeil <ch...@gmail.com>
> 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 do.
> >
> > On Mon, Apr 17, 2017 at 2:24 PM Luciano Resende <lu...@gmail.com>
> > wrote:
> >
> >> 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, 2017 at 11:57 AM, Chip Senkbeil <
> chip.senkbeil@gmail.com>
> >> wrote:
> >>
> >>> 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 <lu...@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.senkbeil@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 <
> luckbr1975@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <
> >>>>>> chip.senkbeil@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/
> >>>>
> >>>
> >>
> >>
> >> --
> >> Luciano Resende
> >> http://twitter.com/lresende1975
> >> http://lresende.blogspot.com/
> >>
> >
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
Re: Uploading PIP for 0.1.0 release
Posted by Luciano Resende <lu...@gmail.com>.
Great, thank you.
On Mon, Apr 17, 2017 at 12:59 PM, Chip Senkbeil <ch...@gmail.com>
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 do.
>
> On Mon, Apr 17, 2017 at 2:24 PM Luciano Resende <lu...@gmail.com>
> wrote:
>
>> 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, 2017 at 11:57 AM, Chip Senkbeil <ch...@gmail.com>
>> wrote:
>>
>>> 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 <lu...@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.senkbeil@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 <lu...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <
>>>>>> chip.senkbeil@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/
>>>>
>>>
>>
>>
>> --
>> Luciano Resende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>
>
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Uploading PIP for 0.1.0 release
Posted by Chip Senkbeil <ch...@gmail.com>.
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 <lu...@gmail.com>
wrote:
> 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, 2017 at 11:57 AM, Chip Senkbeil <ch...@gmail.com>
> wrote:
>
>> 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 <lu...@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 <ch...@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 <lu...@gmail.com>
>>>> wrote:
>>>>
>>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <
>>>>> chip.senkbeil@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/
>>>
>>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>
Re: Uploading PIP for 0.1.0 release
Posted by Luciano Resende <lu...@gmail.com>.
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, 2017 at 11:57 AM, Chip Senkbeil <ch...@gmail.com>
wrote:
> 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 <lu...@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 <ch...@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 <lu...@gmail.com>
>>> wrote:
>>>
>>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <chip.senkbeil@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/
>>
>
--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/
Re: Uploading PIP for 0.1.0 release
Posted by Chip Senkbeil <ch...@gmail.com>.
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 <lu...@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 <ch...@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 <lu...@gmail.com>
>> wrote:
>>
>>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <ch...@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/
>
Re: Uploading PIP for 0.1.0 release
Posted by Luciano Resende <lu...@gmail.com>.
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 <ch...@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 <lu...@gmail.com>
> wrote:
>
>> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <ch...@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/
Re: Uploading PIP for 0.1.0 release
Posted by Chip Senkbeil <ch...@gmail.com>.
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 <lu...@gmail.com>
wrote:
> On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <ch...@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/
>
Re: Uploading PIP for 0.1.0 release
Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Apr 17, 2017 at 8:40 AM, Chip Senkbeil <ch...@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/
Re: Uploading PIP for 0.1.0 release
Posted by Chip Senkbeil <ch...@gmail.com>.
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? 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.
On Sun, Apr 16, 2017 at 2:28 PM Luciano Resende <lu...@gmail.com>
wrote:
> Hi Chip,
>
> Could you please handle the upload of the PIP install artifacts and
> document how to handle that for next releases.
>
> After that, I think we can send the announce e-mail.
>
> Thanks
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>