Release Guidelines v2 #9
Conversation
Updating the release process at 1.0.0 based on OMF staff and WG efforts.
|
@jfh01 @thekaveman I've started a branch and PR to revise the release process and would like your feedback. There's more to add and more to do. Note I am using the word Checkpoint instead of Milestone, since we use Milestone in the Github context and I believe Checkpoint is a more accurate term for what we are intending here too. |
|
Related work on this is happening in the Wikis. Current location of Release Information (MDS repo wiki): I removed some detail from this page, and moved that detail to this Releases page in Governance, and linked to this in the MDS wiki: I added new pages for current and future releases, which show a timeline of events past, present and future. 1.0.0 Release page: 1.1.1 Release page: Note these pages also include the approval timeline, and when the work on the next release should start (with a link to its page), and the timeline broken out into Planning, Development, and Approval phases. These pages will be kept up to date by me (or any OMF admin) as things change, and can be referenced in meetings, docs, online, etc., as the source of knowledge about how a release is progressing and where we are in the process. Note they are chronological in descending order. This is how the other releases have always been documented. I am up for changing it to ascending order. We could discuss what makes the most sense here and elsewhere. Jascha had an idea to make a kind of release table on the branch page, with each item (or was it Checkpoints only?) having a name and a red/yellow/green completion status icon in the other column. Instead for now I have used a green square to indicate "where we are" in the timeline, which moves up as we progress. We could turn the whole timeline into a grid, with a name, date, and color status indicator. Or we could do that for just the Checkpoints, but I think it's good to have the Checkpoints weaved into the greater timeline. This is all in the Governance repo since it's 1) managed by OMF staff and 2) that's where the Release Guidelines are: |
Governance Pull Request
Explain pull request
Updating the release process at 1.0.0 based on OMF staff and WG efforts.
Impact
Describe the impact this change would have on the governance repo and process.
Revising and documenting the release process to align with reality and needs of the community and OMF.
Additional context
Add any other context or screenshots or links about the feature request here.