On Mon, Sep 2, 2019 at 3:42 AM Troy Curtis Jr <troycurtisjr_at_gmail.com> wrote:
> On Fri, Aug 30, 2019, 7:13 PM James McCoy <jamessan_at_jamessan.com> wrote:
>> On Fri, Aug 30, 2019 at 05:12:21PM +0100, Julian Foad wrote:
>> > 2. As 1.13 is only weeks away, there is little point in making any further
>> > 1.12.x patch releases from now on, so I will not plan to do so.
>> > Any other thoughts on anything we ought to include, or to do?
>> Finishing(?) and merging the Python3 support would be ideal. That would
>> give one release for broader feedback before being in an LTS release.
>> I haven't kept up with the status of that branch, nor can I guarantee
>> any time to helping with this, but since you asked... :)
> It needs to get reintegrated with trunk again with the latest changes, but the linux side of the house was looking good. It was in trying to get my Windows Dev environment back up and running again that got me frustrated and gave me an excuse to wander off doing other things... IIRC, there is a build issue with the Py2 bindings in that branch on Windows, but I never got far enough to check it out.
> If there was someone who could help out on the Windows side, I can jump in and get the branch up to trunk and retested in order to get this thing over the finish line.
I might be able to devote some time to this in the coming week(s), if
you can tell me what I need to do / test / validate / ... :-).
Received on 2019-09-02 11:27:58 CEST