| Type of Release | Task |
|---|
| When Task is Due | |
|---|---|
| Major/Minor | Upload to the test/demo environment - http://demo.ole.kuali.org/portal.do |
| 0 (day of release) | |
| Major/Minor | Update https://www.kuali.org/download/ole with links to the source code and release notes |
| 0 | |
| Major | Review the Roadmap's date and features list - https://www.kuali.org/ole/roadmap |
| Post release | |
| Major/Minor | Have all updates in User Documentation pulled into GitHub, see Documentation Standards and Best Practices |
| Day before release | |
| Major/Minor | Have all updates for Technical Documentation pulled into GitHub and linked:
|
| Day before release | |
| Major/Minor | Check that documentation was built with the deployment |
| Post release | |
| Major | Review OLE's acknowledgements and licenses.
|
| Week before release | |
| Major/Minor | Update wiki Home page |
| 0 | |
| Major | Move release notes (under OLE Current Release Status Report) to be child pages of OLE Published Documentation |
| Post release | |
| Major/Minor | Update table under OLE Current Release Status Report with current release; add links to table for release notes, documentation portal |
| 0 | |
| Major | Create Announcement for the Foundation |
| 0 | |
| Major | Blog about the release |
| 0 | |
| Major | Installation instructions for the release |
| 0 through post release | |
| Major/Minor | Review Jiras sited throughout the user documentation to see if notes are still relevant |
Before code freeze | |
| Major | Review user documentation for references to prior/upcoming releases (1.5, 1.6, 2.0, etc) to check for pertinence
|
| Before code freeze |