[Pulp-dev] Publishing an Alpha

[Michael Hrivnak]

Just to tweak the messaging, the plugin API specifically is nearing an
alpha-ready point. As far as I know, we haven't evaluated Pulp 3 as a whole
for alpha readiness.

Installing direct from git would be great, but don't we break that by
having our python packages live not at the root of the repo? Or has pip
gotten smarter about that?  If it hasn't, requiring someone to clone a
local copy of the repo and then pip install from there wouldn't be too bad,
since it's a plugin API alpha intended for developers.

Pushing packages to PyPI sounds good. I wouldn't worry too much about the
pollution aspect, since we wouldn't need to retain them long-term.

I agree that building RPMs or hosting python packages somewhere besides
PyPI sounds like more work than it's worth at this early stage.



On Mon, Sep 11, 2017 at 12:10 PM, Brian Bouterse <bbouters at redhat.com>
wrote:

> Pulp3 is nearing an alpha-ready point which means that it is not yet
> feature complete with the MVP doc [0], but it is ready for some plugin
> writing to be started (or at least planned). I want to check in how how
> we'll release deliver those bits and how we'll install those bits.
>
> ## Proposal (use a git tag)
>
> Tag the alpha with a name like 'alpha1' and push that tag to github. Then
> install directly from github manually.
>
> pip install -e git://github.com/pulp/pulp.git@alpha1
>
> This won't pollute PyPI with a bunch of alphas, and it will let users (and
> QE) install a specific point-in-time snapshot even though new code is being
> merged daily.
>
> ## Alternatives
>
> The second best alternative (I think) is to push the packages to PyPI with
> each alpha release and have pip install from PyPI. I think this would be
> better for betas.
>
> ## Other Alternatives
>
> Other options include hosting the python packages via a webserver, or
> building and distributing RPMs somehow. I don't think either of these are
> viable on the timeline we probably need this on.
>
> Please send ideas or comments.
>
> [0]: https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product
>
> Thanks,
> Brian
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>


-- 

Michael Hrivnak

Principal Software Engineer, RHCE

Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170912/57de4294/attachment.htm>