I think the Devguide is due for some reorganization after the migration.

In particular:

• The version control setup section should link to a separate "git" page (either thepullrequest or thecommitting page -- see below). (seeUpdate the setup and PR lifecycle pages #265)
• The compile and build section should be reorganized. (seeReorganize the setup.rst page. #412)
• The lifecycle of a PR page seems to expand on the quick start, but doesn't include detailed setup instructions and git commands. This page seem to be aimed at contributors (seeUpdate the setup and PR lifecycle pages #265). Also the Generation section should be under Preparation, alongside another subsection about running tests.
• The runtests page expands on a paragraphpullrequest/preparation.
• Thesilence warnings andfixing easy issues are both 2-paragraphs pages that might be moved as sections of other pages.
• Thetracker andtriaging page should be updated and perhaps merged (seeUpdate the devguide with the discussion on bug triage #308 andUpdate triage page with tables #339).
• Thewhere to get help andfollowing Python's development could be merged.
• The committing page seems to be aimed to core-dev, but since now the workflow for both core devs and contributors is quite similar, it should perhaps be merged with thepullrequest page. Parts of this page should be moved to other pages, and only the content relevant to core devs should be left there. (seeUpdate wording on committing.rst. #262 andReorganize git commands #263)
• The continuous integration page should be updated. (seeUpdate buildslave.rst page for Buildbot 0.9.x #290)
• Theexperts page should be moved closer to thedevelopers page. (seeReorganise the devguide to directories #901)
• The mercurial for git developers page is now unnecessary, and it should either be removed, or better reversed and become "git for mercurial developers". (seeDelete the "Mercurial for git developers" page #258)
• The adding to the stdlib page should first list what are good and bad addictions (with examples) and then explain the process to add something (seeIdea: mention 3rd party "extended stdlib" modules in developer guide #35).

The other pages don't have any major issue :)