> My preference is to drop 3.0 entirely (no incompatable bugfix release) > and in early February release 3.1 as the real 3.x that migrators ought > to aim for and that won't have incompatable bugfix releases. Then at > PyCon, we can have a real bug day and fix-up any chips in the paint. I would fear that than 3.1 gets the same fate as 3.0. In May, we will all think "what piece of junk was that 3.1 release, let's put it to history", and replace it with 3.2. By then, users will wonder if there is ever a 3.x release that is any good. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4