[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: Nathan Hartman <hartman.nathan_at_gmail.com>
Date: Thu, 14 Nov 2019 00:46:49 -0500

On Wed, Nov 13, 2019 at 12:06 AM Nathan Hartman <hartman.nathan_at_gmail.com>
wrote:

> > If the following looks like a reasonable start, I'd like to go ahead
> and commit it (and continue editing/fixing/improving)...

r1869776: I committed most of the text discussed earlier to **staging**.

More below:

On Tue, Nov 12, 2019 at 6:59 AM Julian Foad <julianfoad_at_apache.org> wrote:
> 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?
>
> 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.

To address this, I added the text I posted here earlier in a separate
commit:
r1869777

To see all of the above, visit:
https://subversion-staging.apache.org/docs/release-notes/1.14.html

All thoughts, suggestions, and improvements are welcome.

In particular there is a TODO item to figure out and describe which
versions of Python 3.x we support in 1.14.

Cheers,
Nathan
Received on 2019-11-14 06:47:06 CET

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