Add updating documentation to the release checklist

Author: sbarzowski

release_checklist.md

@@ -1,5 +1,5 @@
 # Checklist for building Jsonnet releases
-  
+
 ## Are jsonnet & go-jsonnet in sync?
 1) Check out master from both
 1) Check go-jsonnet/cpp-jsonnet submodule is HEAD of jsonnet tree, if not:
@@ -22,6 +22,8 @@
 find test_cmd -name '*.cpp' -o -name '*.golang' -o -name '*.stdout' -o -name '*.stderr' -o -name 'stdout' -o -name 'stderr' | \
   xargs sed -i 's/ v0[.][0-9.]*/ NEW_VERSION_GOES_HERE/g'
 ```
+1) Check if any changes to the documentation are necessary by checking commits since previous release (especially stdlib additions).
+1) In stdlib documentation replace any "Available in upcoming release." with "Available since NEW_VERSION_GOES_HERE".
 1) `python setup.py build sdist`
 1) `twine upload dist/whatever.tar.gz`  (Needs credentials on pypi)
 1) ON ANOTHER MACHINE AND CHECK THAT THE VERSION IS CORRECT AND IT ACTUALLY IS BUILDING THINGS IN THE LOG: `sudo pip install jsonnet --pre --upgrade`
@@ -36,10 +38,10 @@ find test_cmd -name '*.cpp' -o -name '*.golang' -o -name '*.stdout' -o -name '*.
 1) Remove -pre from version in `include/libjsonnet.h`
 1) Update version in `CMakeLists.txt`
 1) Update `test_cmd` golden file version numbers
-1) run test again! 
+1) run test again!
 1) commit and push
 1) Make release in github, write release notes by checking commits since previous release
 1) `python setup.py build sdist`
 1) `twine upload dist/whatever.tar.gz` (the version without the -pre)
 1) Post to Jsonnet Google Group
-
+1) Update the live version of the website