Phabricator has a blocking task with a laundry list of bugs to fix before a 2.0 release T72936
We should put out a release candidate, or two, before then, to attract early adopters who can report issues.
Im told only Merlijn and Xqt hold the keys necessary to actually upload a release into pypi.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | jayvdb | T1315 Release 2.0 | |||
| Resolved | valhallasw | T76262 Release 2.0 RC1 | |||
| Resolved | None | T85328 PEP-8 compliance | |||
| Resolved | Xqt | T87409 pep8 E402 vs __version__ and others | |||
| Declined | None | T101593 Pywikibot use of $Id$ fails on git installed on Redhat boxen | |||
| Resolved | JanZerebecki | T87169 run at least pep8 and pep257 for new changesets submitted to pywikibot/core for any user | |||
| Resolved | Huji | T231219 [pep8] section is deprecated. Use [pycodestyle]. | |||
| Resolved | jayvdb | T114534 release 2.0rc4 | |||
| Declined | None | T101587 Convert wiki pages for 2.0 into phabricator tasks | |||
| Resolved | jayvdb | T114464 Pywikibot 2.0 should be Python 2.7, 3.3 and 3.4 only | |||
| Declined | None | T121948 Pywikibot 2.0rc5 |
IMO T85328: PEP-8 compliance isnt suitable for 2.0 now, as 2.0 is in serious release candidates mode now, and so should be stablising and only contain critical bug fixes.
Can the critical bug fixes be mentioned by adding them as subtasks ? This would give more clarity to find things and also to see how close we are to the next release