I just learned that there is a release-team email list as well, so I'm including that list too.

 if we're pulling release notes to post on the kbase site, just a reminder that we need to make sure we are pulling them from the git versions that are tagged for release, not just the latest on master.  For instance, in 'trees' I've already started some notes since the last release that shouldn't be posted until we complete the next future release.  This should also help us to ensure that we are not posting release notes for services that aren't being released.

Yes, this was our concern too.  Can git.kbase.us:<service_name>/RELEASE_NOTES.txt be pushed to http://www.kbase.us/services/docs/<service_name>/ on deployment, so that api and release note documentation updates on kbase.us aren't done two different ways?

Thanks,
Neal