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. [1] https://about.gitlab.com/ > One problem with this is that now our process requires some manual work > which takes some to make a release. I still think it should be manageable, at least if it's documented how to do a release and how to use devpi-cloud-tester for everyone. Haven't checked in a while. > > As such i would like to stop using a features branch at all and return > > > to having only master. > > > > And not have any bugfix releases? > > > > Having only a master branch, I think Ronny was proposing to then figuring > out if it was a bug fix release or a minor release based on the CHANGELOG. That means you either need to arbitarily hold back contributions, or you lose the ability to do bugfix releases and need to do a feature release (probably with new subtle bugs, looking at our track record) every time. Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
