Message292716
| Author |
serhiy.storchaka |
| Recipients |
benjamin.peterson, cgohlke, cstratak, hroncok, larry, ned.deily, njs, serhiy.storchaka, skrah, steve.dower |
| Date |
2017年05月02日.06:18:27 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1493705907.82.0.0240382272528.issue29943@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Either 3.6.1 or 3.6.0 should be officially declared broken. If declare 3.6.1 broken we must port PR 1049 to 3.6 and release 3.6.1.1 or 3.6.2 as early as possible. Many third-party extensions built with 3.6.1 should be rebuild with a new release for compatibility with 3.6.0. Distributors should update Python to a new release. If declare 3.6.0 broken we shouldn't do anything beside this. Distributors should update Python to 3.6.1, as planned.
Ned, what is your decision as RM? |
|