On Mon, Jan 25, 2016 at 12:03 +0000, Bruno Oliveira wrote: > On Mon, Jan 25, 2016 at 10:00 AM Ronny Pfannschmidt < > [email protected]> wrote: > > > For bugfix releases i would like to do them as soon as possible > > (i.e. try to stay within one day of the merge) > > > > Hmmm what do you mean Ronny? A release after each bug fix is merged in? > > that would also create more incentives for an better automation > > > > I agree, that certainly would be a benefit.
If we directly release after bugfix merges there is not much chance humans will use it and discover problems. I'd really like bugfix releases to be stable series and i consider that more important than quick releases. So unless we have more thorough testing not only of pytest itself but of the 10-20 most popular plugins and maybe a few example projects let's not increase the pace to "release after bugfix merge". btw, how many people have said that pytest is too slow on releases? In fact i know that several companies are holding back on upgrading, some using much older versions. For them, upgrading is not automatic but a more tedious process involving communication across teams etc. That doesn't mean we need to slow down but just that there are various perceptions on release schedules. holger > Thanks, > Bruno. > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
