Quick Introductions
Overview
Q1. What is beneficial about our current release notes Morning Glory (R2 2022) Release Notes?
- Content (plain language) to explain issues
- Sorted by area of functionality (first table)
- Easy to contact the person responsible for each area (easy to sort/group)
Q2. What is unclear about our current release notes?
- Not scannable/ Not easy to find things
- Descriptions are not detailed enough when posting a JIRA link. Need to provide more details.
- Comment column is not used
- Group: What needs to be done before a release upgrade Then another group for during and Then another group for after
- Group by functional area
- added by MF after meeting: hard to find the release notes in the first place, no link on main wiki page https://wiki.folio.org/ for Nolana release notes
- added by MF after meeting: for sections that are generated from JIRA issues, like the "Additional Known Issues" section in Nolana release notes, it isn't obvious that only the first 20 (or however many rows) are shown, and if there are more than 20, you have to do another click to see the full list of issues
Q3. What is missing with our current release notes?
- A way to engage with release notes? Be able to make a comment / ask a question.
- Maybe a release Kanban board
Q4. Have you reviewed release notes from other products/companies that you thought did a great job? If, so, please post links.
- Noora
- https://roadmap.thestorygraph.com/changelog
- https://miro.com/changelog/ these are weekly product updates, vs batched in releases, but I especially like how they have animations playing that show what the new features are, without the reader having to click to get more info. (MF)
Action items for next week
- Review above responses
- KG will investigate a Kanban release board
- Create quick poll
- GG: create Google Form
- EG: Check if Confluence has a way to make better release notes