[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: Tue, 3 Dec 2019 15:14:10 -0500

On Sun, Dec 1, 2019 at 6:32 PM Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Nathan Hartman wrote on Sun, Dec 01, 2019 at 10:58:34 -0500:
> > On Thu, Nov 28, 2019 at 4:05 PM Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> > > Y'all might consider starting a wiki page or a jira issue tracking
> > > the categorization. I think it might be helpful to tracking the
> > > work done/punted/pending.
> >
> > Agreed. I just wanted to get an initial list that is more-or-less
> > accurate first. I think we're at that starting point now.
> >
> > Now, I wonder, how should we handle updates to the list as work
> > progresses? With the wiki we can move items around in the list. With a
> > Jira issue, would we add a comment with an updated list each time
> > item(s) change status?
>
> I suggest to just go ahead and create the wiki page.

Created the wiki page:
https://cwiki.apache.org/confluence/display/SVN/Subversion%27s+Python+3+Support+Status

I also added a link to it from the ManyHands page.

The purpose is to keep track of Python 3 support throughout all of our
scripts while work progresses to make everything compatible, so please
discuss any findings/changes/additions/observations here, or (if you
prefer) feel free to update the wiki directly...

I'm placing a reminder to myself to update the 1.14 Release Notes with
a link to this wiki page in "known issues" as discussed previously...

Cheers,
Nathan
Received on 2019-12-03 21:14:30 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.