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. > > [1] https://about.gitlab.com/ from my pov it should be valid to release once a week and simply up numbers depending on whether patches or features are in >> 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. https://github.com/pytest-dev/pytest/blob/master/HOWTORELEASE.rst is about 13 steps, most manual mundane and error-prone - it should be at most 1-2 steps
> >>> 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. if we make releasing inexpensive and reliable even a botched release an have a quick fix afterwards, i don't see a problem there, as long as we have processes in place that let stuff like "softening of xfail" to happen we'll have botched feature releases anyway, and IMHO that shouldn't stand in the way of removing unnecessary maintenance pain. what i want to remove is time eating and painful processes at releasing, -- Ronny > > Florian > _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
