Update README.md (#5519)

clarify some points, add links, add doc/conf.py

Author: devyte

package/README.md

@@ -103,15 +103,15 @@ The following points assume work in a direct clone of the repository, and not in
    git push origin 2.5.0
    ```
 
-5. Wait for Travis CI build for the tag to pass. Check that the new (draft) release has been created. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.
+5. Wait for Travis CI build for the tag to pass, see https://travis-ci.org/esp8266/Arduino/builds. Check that the new (draft) release has been created, see https://github.com/esp8266/Arduino/releases. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.
 
 6. Check that the package index downloaded from http://arduino.esp8266.com/stable/package_esp8266com_index.json contains an entry for the new version (it may not be the first one).
 
-7. Navigate to release list in Github, press "Edit" button to edit release description, paste release notes, and publish it.
+7. Navigate to release list in Github here https://github.com/esp8266/Arduino/releases, press "Edit" button to edit release description, paste release notes, and publish it.
 
 8. In the issue tracker, remove "staged-for-release" label for all issues which have it, and close them. Close the milestone associated with the released version.
 
-9. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that "stable" points to that build. If a new build did not trigger, log into readthedoc's home and trigger it manually.
+9. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that "stable" points to that build. If a new build did not trigger, log into readthedoc's home here https://readthedocs.org/ (account must have been added to project as maintainer) and trigger it manually.
 
 
 10. Create a commit to the master branch, updating:
@@ -121,3 +121,6 @@ The following points assume work in a direct clone of the repository, and not in
    * In main README.md:
 
      - in "Latest release" section, change version number in the readthedocs link to the version which was just released, and verify that all links work.
+   * In doc/conf.py
+   
+     - update version and release to the *next* milestone