Release Process

GitHub Issues

1. Ensure all milestone tickets have been addressed / closed

Content Updates

1. Copy "draft" into new "version named" directory
   • Replace "respec-w3c-common.js" with "respec-ocfl.js"
   • Add directory "css-js" from previous version
2. Update "version/spec/index.html"
   • new "title"
   • new "meta:content"../respec-ocfl.js"
   • change "script" to =
   • "respecConfig:publishDate" = whatever it is
   • "respecConfig:specStatus" = "ocfl-cr"
   • new "Previous version" ('value' and 'href')
3. Update "version/implementation-notes/index.html"
   • new "title"
   • new "meta:content"
   • "respecConfig:publishDate" = whatever it is
   • "respecConfig:specStatus" = "ocfl-cr"
   • new "Previous version" ('value' and 'href')
4. Update README.md
   • "This version"
   • "Latest stable version" = N/A until 1.0
5. Update "index.md" to include links to latest release
6. Commit in Github with message: "Create [Alpha|Beta|None] X.Y release"
   • Via pull-request
7. Once pull-request is merged:
   • tag release as 'x.y'
   • create GitHub release page

Emails

1. Post message to following lists
   • PASIG
   • Fedora
   • Code4Lib
   • Samvera
   • Islandora
   • DSpace
   • Educause Lib-IT