On Wed, Jan 13, 2021 at 9:04 AM Ralf Gommers <ralf.gomm...@gmail.com> wrote:
> > > On Wed, Jan 13, 2021 at 4:41 PM Matti Picus <matti.pi...@gmail.com> wrote: > >> This message ended up in my spam box for some reason, sorry for the late >> reply. >> >> >> We typically release a new version twice a year, and support two >> versions at a time. So right now we are releasing version 1.20 and will >> support 1.19 and 1.20 for the next period. When 1.21 is released, we >> will support 1.20 and 1.21. Support for the released version is limited >> to bug fixes. >> > > Is this two-version thing actually something we're committed to doing? > Chuck started doing it at some point, which as release manager is his > decision - but I don't think we ever really decided or announced this as a > policy. > > If we're committed to it, we should probably mention it somewhere in the > docs or release how-to. And I should go update our Tidelift data. > > Cheers, > Ralf > > We only support *one* version at a time. Supporting two is hard, backports become difficult. The only time we have supported two was the 1.16.x LTS release. At the moment things are a bit different because we are waiting on pyarrow before releasing 1.20.0, it is a temporary measure. The binannual release cycle is because 300-500 merges per release felt about right. If the merge rate goes way up and stays there we may release more often. But that is unlikely unless we get a lot more support. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
