Mismatch of python install requirements between web documentation and v2.5.0 release.

[patrickwalton]

I cloned the repository and checked out the latest release (v2.5.0). In following the install instructions online, I noticed they include the following line:

Ensure all build related pip packages are installed:

(venv) $ pip3 install -r requirements_dev.txt

But the v2.5.0 release doesn't have requirements_dev.txt, only requirements.txt and requirements_optional.txt.

I see that the online documentation main page shows "Status: version 2.5.38" in the sidebar.

Is the disconnect here coming from the online documentation being tied to the develop branch? Is there a way to let the viewer select the branch for the documentation? If not, can we change the online documentation to show the latest release, not the develop branch? Users of the develop branch will typically be more equipped to build the specific documentation for that branch than users cloning the most recent stable release.

I also noticed the requirements_dev.txt uses specific versions for packages, which is really important for consistent release builds. Thank you!

[patrickwalton]

Closed because I decided this should be an issue: #913