[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Merging branches/swig-py3 to trunk

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 12 Nov 2019 12:09:03 +0000

Julian Foad wrote on Tue, 12 Nov 2019 11:59 +00:00:
> A thought about supporting older Python versions... Somewhere in the
> pipeline between community inputs and project outputs, should we
> distinguish between "we will not support ..." and "we will be glad to
> accept contributions that enable supporting ..."? How would this look?

We could say that Python >=3.5 are "tier 1" supported and Python <=3.4
are "tier 2" supported, in the sense that, for example, a bug that
affects Python <=3.4 only will not be considered a release blocker, but
patches for py<=3.4 will still be accepted, to facilitate developing svn
1.14.x on LTS distros that still package py3.4. [Here, 3.5 is the
oldest non-EOL Python minor line.]

> I am just getting the feeling that we, a small group of developers, are
> trying to make a decision by ourselves when perhaps we should be more
> actively reaching out to the wider community to invite them to influence
> the result. I know we have to decide to write something, but maybe we
> can write something that encourages the users (yes, the tiny proportion
> that might do something about it) to feel they can have a stake in it if
> they want to.
>
> - Julian
>
Received on 2019-11-12 13:09:29 CET

This is an archived mail posted to the Subversion Dev mailing list.