1) Before sending out communications, insure that following documentation is updated:
- https://source.sakaiproject.org/release/(release id). For example https://source.sakaiproject.org/release/10.0 goes to the 10.0 release - access needed to sakai-static.wnmh.net through Wush.net and the directory is copied (cp -r) from the previous release directory and then updated. Go to /home00/sakai/public_html/release to find and create the relevant directories.
- https://github.com/sakaiproject/sakai - update the ReadMe.md on github.
- Release Documentation
- Confluence Release notes, especially summary of new features and technical requirements
- Sakai Release Date list
- Before updating the public website (www.sakaiproject.org), make sure to redirect http://source.sakaiproject.org/release/ to point to the latest .x release (where "x" is latest maintenance release) directory by updating the index.html file the sakai-static.wnmh.net in the ~/www/release directory.
- http://www.sakaiproject.org at the following places
- http://nightly2.sakaiproject.org - assuming the QA server is at least temporarily set as the release. - "QA test server on MySql". update under "Schedule" (for now. working on an improved html page).
- Complete list of Jiras on the release page - go to the JQL and add the ids for the projects so we are showing the full list of updates in 11, not just incremental).
- The Sakai section on the Apereo website reflects the latest version, with appropriate links to Sakai site and blog, if applicable.
2) Communicate technical details, specifically how to access the release artifacts, to the QA, Dev, and Prod lists
3) Communicate to the broader community the main changes, in non-technical terms, for the release. Include QA, Dev, Prod and add Internationalization, Accessibility, Sakai User, Pedagogy, and Documentation.
4) Post a highlighted news item to the Apereo.org web site.
5) Social media - Post to Facebook as Sakai Project by adding a Milestone and to Twitter as a Tweet from SakaiProject
6) Send out an Apereo Announcement
7) Should go to outlets outside of the community (Educause... others?)
8) Security report should go to firstname.lastname@example.org within a week after the release, at most.
9) Press release? Check with Ian D.
10) Update version data in JIRA (ie. set release date, create a placeholder for a future maintenance release, etc). Sakai, KNL, LSNBLDR, Samigo.