I don't think there is a problem with that. Please note that as far as Apache
is concerned any artefact consideres to be "Apache superset" needs to be
available from it's official release location. So it's fine to "copy" this over
to pypi/docker but not to have a "different" release at those loc
Oh no, looks like someone claimed "apache-superset" on pypi.org, probably
by mistake. https://pypi.org/user/cidiomar.dias.restoque/
On Fri, Aug 9, 2019 at 3:24 PM Maxime Beauchemin
wrote:
> Airflow does it, so yes it's doable. Though we'll have to change the pypi
> package name to `apache-supers
Airflow does it, so yes it's doable. Though we'll have to change the pypi
package name to `apache-superset`. I think it's fair to push an RC as part
of the RC release process.
Max
On Fri, Aug 9, 2019 at 2:55 PM Charles Givre wrote:
> My .02 would be to do all of the above. Personally, being a
My .02 would be to do all of the above. Personally, being able to install
Superset via pip was really useful in starting the Superset journey... I would
also recommend an official Dockerfile. I'm not sure why you wouldn't want to
push it to DockerHub, but if you want to make it easy to adopt
Hi all,
How should we go about convenience releases? Currently I'm thinking
Pypi.org, but we could think about Docker / DockerHub as well.
First thing to know is that a convenience release for Superset is likely to
contain minified [aka "compiled"] javascript out of hundreds of libs. In
theory th
