Re: Merging branches/swig-py3 to trunk

Branko Čibej wrote:
> [...] I propose that:
>
> 1. we release 1.13.0 as planned next week when the soak period ends
> (pending any last-minute critical bugs found, of course);
>
> 2. immediately after the 1.13.0 release, we merge the swig-py3 branch
> to trunk; and,
>
> 3. proceed with 1.14.0 as planned.

+1. Thanks for proposing a specific plan.

> *If* we find there's lots of user demand for Python 3 support, we can
> always release 1.14.0 early as a regular release, [...]

Yes, we can still consider something like that as an option.

> Given the planned EOL of Python 2, I will, in the following weeks,
> change the (macOS) build slaves I control to build with Python 3 [...]

Excellent. Thanks.

> Last but by no means least, I'd like to thank everyone who helped make
> this rather important feature work:
>
> $ svn info --show-item=relative-url
> ^/subversion/branches/swig-py3
> $ svn log --stop-on-copy | egrep '^r\d+ \|' | cut -d '|' -f 2 | sort -u
> cmpilato
> danielsh
> futatuki
> luke1410
> troycurtisjr

Indeed. Seconded.

- Julian
Received on 2019-10-23 15:23:13 CEST