Re: Project Planning
"Thomas A. F. Thorne" <[email protected]> Thu, 13 Oct 2016 14:25:32 +0100
| Newsgroups | gmane.comp.compilers.distcc |
|---|---|
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============4426712613631707940== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dAlXpTikVch9D5Hsjdo9mnA004tadIUps" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dAlXpTikVch9D5Hsjdo9mnA004tadIUps Content-Type: multipart/mixed; boundary="LMWkLEubUUW25e53fweG7akuE9b6H1EwH" 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]> <[email protected]> In-Reply-To: <[email protected]> --LMWkLEubUUW25e53fweG7akuE9b6H1EwH Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Dropping Python 2 Support (or more specifically moving up to python2.7 from python2.4 on a maintenance branch and dropping python3 support from master) Having looked into starting a 3.2 release or 3.2_maintenance branch I stumbled into the https://github.com/distcc/distcc/pull/177 request.=20 Under that request the creation of the 3.2 maintenance branch is suggested and it is proposed that said branch will be used to maintain some support for Python2.7 for as long as it seems necessary. =20 The main work would continue on master, with the creation of a 3.3.# release in the near future. The master branch (and therefore the 3.3 releases onwards) would require python3.=20 What do the viewers of this list think of the proposal?=20 Silence will be taken as support. If the action is supported I will try an action at least some of it at the end of the month. Regards, Thomas --LMWkLEubUUW25e53fweG7akuE9b6H1EwH-- --dAlXpTikVch9D5Hsjdo9mnA004tadIUps 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/4tNAAoJEPXLKKkUazGAsMUIANMd8y+2D0/0qcMQq43eIvjI +SiVyHYnUgk+Nm/B+9Xbs7JLgl9+LGlxmXRfQoiw5sYf5vXvgr7YZnx3y9r4x0Tn Tmoq4l1LDXaBc3v02Ed/dYJXPGNW+WLq9o3CXUybhQg2h+f39k7b3otXY9mz/Swe ATI6tdBl35GSnAcjYq/ubxJpFSeb6k6WHVilnC77TLYsP59e4+y9xdifxTLVPKjl ZDtPvpveHExQrskIN6uSWBF+XULuebQi2xwaapv1jAECS7sK7gVNdiTNYYfe89n6 gA6C2IYtvB/lrbDXpRrPL4lPc9961/5smV9Yh34gujNd7tuwBEB/9dFvMgzuN7g= =bneS -----END PGP SIGNATURE----- --dAlXpTikVch9D5Hsjdo9mnA004tadIUps-- --===============4426712613631707940== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X18KZGlzdGNjIG1haWxpbmcgbGlzdCAgICAgICAgICAgIGh0dHA6Ly9kaXN0Y2Muc2FtYmEub3Jn LwpUbyB1bnN1YnNjcmliZSBvciBjaGFuZ2Ugb3B0aW9uczoKaHR0cHM6Ly9saXN0cy5zYW1iYS5v cmcvbWFpbG1hbi9saXN0aW5mby9kaXN0Y2M= --===============4426712613631707940==--