Re: Project Planning

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============4026076741393779931==
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="QVx8xsJiwSjGsOcdPqmoQSQ2k5DWeM3ub"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--QVx8xsJiwSjGsOcdPqmoQSQ2k5DWeM3ub
Content-Type: multipart/mixed; boundary="HBMWLsQSWSW6QUL4FjwahnK5Eb9Fu7sTI"
From: "Thomas A. F. Thorne" <[email protected]>
Reply-To: [email protected]
To: =?UTF-8?Q?Anders_Bj=c3=b6rklund?= <[email protected]>,
 "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Subject: Re: Project Planning
References: <[email protected]>
 <[email protected]>
In-Reply-To: <[email protected]>

--HBMWLsQSWSW6QUL4FjwahnK5Eb9Fu7sTI
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


On 08/10/16 13:50, Anders Bj=C3=B6rklund wrote:
> I suppose you want to do some 3.3 releases from master, at some point.
> But tagging the 3.2rc1 and doing some 3.2.x release would be a start ?
Sounds like a reasonable idea to me.=20

> The suggestion was to do the branch-out of 3.2-maint _before_ changing
> from python to python3.=20

This also sounds sensible.  There are 74 issues currenlty on the git site=
 of the project.  There have been a lot of changes since the 3.1 release =
we have tagged so drawing a line in the sand my kicking off a 3.2 release=
 would be a good start. =20

We can deside which issues are enhancments and bugs.  Which are high, med=
ium or low priority.  Then make a commitment to try and fix the high prio=
rity bugs on the 3.2 maintenace line which will be maintained for Python =
2 for now. =20

Following that we can decide if we want to try and support Python 2 & Pyt=
hon 3 or just Python 3 in the 3.3 and onwards releases.  I know that Ubun=
tu and a few other systems are swtiching of ther 3 being the default. =20

Regards, Tom=20



--HBMWLsQSWSW6QUL4FjwahnK5Eb9Fu7sTI--

--QVx8xsJiwSjGsOcdPqmoQSQ2k5DWeM3ub
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX/4LvAAoJEPXLKKkUazGAbZcIAM6lF74ZoERgYvQ8F2pfAMTX
CfHU5jKx1+u89VPuRbiIr3Q1/n3eyXcgd2S1RjadgE9trVL10tupV1MhB5erNaND
V3/9YcDZn1tlGDK+b49SqV3ywBYwqn21jJzGDo8zatKyn0M4dgcQYAkIuTKmHvl+
kO5Rb5gTnAEoYRavwohUUeWLa6KEVqGFnpz1FT46cYVxrQL85u1nn/jJUHtDCwXZ
Sul4Y2MOhwvc6NLkdE6TF9DedypzIE9txYPIe7zAkZRDWgdGhGgueitlugrDDMC6
cLszzt7/Og8cG8xUYuN3OrLYACH7CEq32LQGZC5s9VlzL4R0JivBKfW+9aSoOoI=
=JKnh
-----END PGP SIGNATURE-----

--QVx8xsJiwSjGsOcdPqmoQSQ2k5DWeM3ub--


--===============4026076741393779931==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X18KZGlzdGNjIG1haWxpbmcgbGlzdCAgICAgICAgICAgIGh0dHA6Ly9kaXN0Y2Muc2FtYmEub3Jn
LwpUbyB1bnN1YnNjcmliZSBvciBjaGFuZ2Ugb3B0aW9uczoKaHR0cHM6Ly9saXN0cy5zYW1iYS5v
cmcvbWFpbG1hbi9saXN0aW5mby9kaXN0Y2M=

--===============4026076741393779931==--