Hey everyone, There are various things in this thread I want to answer to, so I'll just answer to three mails in one :)
On Wed, Jul 29, 2020 at 10:43:21AM +0100, Sorin Sbarnea wrote: > There was nothing wrong with pytest release process, there was a pre-release > and also enough time to raise bugs... only if someone would try that > pre-release before the release was made. Experience told me that less than > 1/1000 users will try it. FWIW things aren't nearly as bad as you claim them to be. Just because not *all* issues were caught during the pre-release, that doesn't mean *none* were. Notably, Miro Hrončok tested the RC against all Fedora packages using their infrastructure, but various other users also caught regressions, both in pytest itself and plugins. See e.g. https://github.com/pytest-dev/pytest/issues/7532 This allowed various regressions to be fixed before the release, as well as updated releases for various plugins (pytest-xdist, pytest-forked, ...) before shipping the release. Clearly, that was a success. Was it less than 1/1000 of all users? Probably, given that pytest probably has hundreds of thousands of users. Was it "nobody" like you claim? Definitely not. > An external contributor is not able to @mention a maintenance team (in fact > no proofs that it even exists) so PRs may be lingering for a while or ever > without knowing who could be able to help moving them. Only practical > solution I found so far was to dig the commit history and make guesses who is > likely to be a core, dig for his online contacts and hope he receives your > call and happens to be available or willing to help. Clearly the (former?) maintainer of that plugin did see your message: https://github.com/pytest-dev/pytest-html/issues/318 > How are users expected to contact those with power of making a change on any > project under pytest-dev organization? I'd say by opening an issue in the respective repository. > Is this mailinglist the only option? If the people maintaining that plugin don't respond, then I'd say this mailinglist is the right place. > Why not an online forum, where anyone can do a social login and post a > message/reply or watch a specific topic he is interested in, without having > to expose his email and subscribe to far more than he may want? Two easy > alternatives are either Github discussions (beta opt-in, can provide details) > or just using https://discuss.python.org/ -- where we could use a category or > tag, which both can allow subscript, in addition to topic subscription. -1 on further fragmenting people by having even more communication channels. That'll lead to the exact opposite of what you probably want, as you'll reach *less* core maintainers than via an already established and widely used channel. If you want to get in touch with people responsible for a given plugin, use the repository. If that doesn't work and you want more pytest maintainers to be aware of the problem (and perhaps find someone to jump in with maintaining it), then you *do* want to reach out to more people than just the ones who'd be subscribed to a given plugin, no? On Wed, Jul 29, 2020 at 12:22:50PM +0200, Jim Brännlund wrote: > I’m not sure Travis supports (or allows it for free tier) scheduled runs. It does (and so does GitHub Actions, FWIW). On Wed, Jul 29, 2020 at 01:16:06PM +0100, Thomas Grainger wrote: > We could add a script in each repo that takes the latest pytest version and > updates the relevant config, then use asottile all-repos to run those > scripts with any new versions Why? Something like a tox environment running against the latest pytest prerelease (or pytest master even) plus a scheduled build job should totally suffice, no? Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
