On Wed, Apr 19, 2017 at 11:42:29AM +0000, Bruno Oliveira wrote: > On Mon, Apr 17, 2017 at 3:49 PM Ronny Pfannschmidt < > [email protected]> wrote: > > > > > On 14.04.2017 14:17, Florian Bruhin wrote: > > > On Thu, Apr 13, 2017 at 05:51:34PM +0000, Bruno Oliveira wrote: > > >> What if we instead of considering features, we released a new minor > > version > > >> periodically, for say every month or two? We could adopt the same for > > bug > > >> fix releases, like each two weeks. > > > FWIW what GitLab[1] does is a monthly feature release, and patch > > > releases whenever needed. I don't think it's a good idea to have a fixed > > > release cycle for patches, but it sounds like it could work quite well > > > for feature releases indeed. > > > > I'm curious, why do you think it is not a good idea to have a fixed or > semi-fixed release cycle for patches?
Sorry for the late answer, somehow that mail made itself comfortable in my inbox for a while ;) I just think it doesn't scale well. If we do something which breaks a lot of testsuites we don't want to wait with doing a patch release - and at the same time if we just have some doc fix or even a change which isn't user-facing at all, doing a release just causes unnecessary work. Even if we automated our part, releases always mean work for downstreams like distributions or users with pinned dependencies. Because of that, I think it makes more sense to be a bit more flexible with patch releases. Florian -- https://www.qutebrowser.org | [email protected] (Mail/XMPP) 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 [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
