Hi all,

the current build seems fine to me, so I would like to push that to pypi tomorrow evening if nobody objects.

BTW: I am wondering if it might be better to track releases on the issue tracker as well, as this would get more visibility there ...

Cheers,

Oliver

On Sat, 1 Apr 2017 at 21:58 Oliver Bestwalter <oliver@bestwalter.de> wrote:

On Sat, 1 Apr 2017 at 18:16 Florian Schulze <mail@florian-schulze.net> wrote:

Do you plan to only upload release candidates as dev releases, or more
frequent? I'd be fine with the former, but I don't like if PyPI is
spammed with dev releases. I mean devpi was created for this exact use
case. And I don't see much difference in installing with "pip --pre"
versus "pip -i ..." on a CI.

I was thinking only of release candidates and pushing them to pypi instead of devpi as that removes the dependency from another service that has to be up, if people add it to their CI settings. But if devpi.net is meant for this kind of thing and is reliable enough, let's leave the pre releases on devpi and only push the actual releases to pypi.

Cheers,
Oliver