[pytest-dev] transfer repo / pypi access / ML announce

[Sebastian Rahlf]

Little word of caution: Not all plugins are on github/use git.
Travis will only work with github projects afaik.

Sebastian

2016-09-14 14:01 GMT+02:00 Ronny Pfannschmidt <
opensource at ronnypfannschmidt.de>:

> sounds good to me,
>
> can we up the release automation requirements,
> so git tag + travis deploys can be used for releasing?
> best, Ronny
>
>
> On 14.09.2016 13:58, holger krekel wrote:
>
> I am a bit concerned that people who transfer repos to pytest-dev think that it receives magic maintenance because this relevant section in the docs
> http://doc.pytest.org/en/latest/contributing.html#submitting-plugins-to-pytest-dev
>
> is not very explicit about it, even says "sharing some of the maintenance responsibility".  I suggest we explicitely say that maintainers are generally expected to continue maintaining their plugins.
>
> And how about having a "pytest-dev" user which has release rights on pypi for all pytest-dev plugins?  The credentials could be shared in a file in our public repo, encrypted to known GPG public keys. Speaking of which, we could collect gpg keys of contributors in another file.
>
> lastly, if we had a pure pytest-announce mailing list we could announce new pytest-dev plugins (from time to time) and releases there. We can certainly get that list on python.org.
>
> best,
> holger
>
>
>
>
> _______________________________________________
> pytest-dev mailing listpytest-dev at python.orghttps://mail.python.org/mailman/listinfo/pytest-dev
>
>
>
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20160914/14164094/attachment.html>