Page Comparison

First Principles

...

• QA recordings very helpful
  • Narration and subtitles 
    • Be helpful for PO and Dev reviews too. 
  • animated gifs
  • need to include in release with context (i.e. link to JIRA or description)
• Timeliness
  • Release notes - PO contact list and disclaimer 
  • Have Release notes deadline tied to Module release deadline 
• Release/Developers checklist that includes a task for release notes 

To do Action items for Feb 23

• KG will send a note via slack to PC/TC/FOLIO implementers/POs regarding this group THEN Gloria can send out the survey 
• KG contact Oleksii about the Timeliness section 
• KG - I will post a proposed Release/Developers checklist to the group for review 
• GG - will update survey 
• All - Feedback on PO features pages. Any value including with release notes 
  • Display a history of edits for the order record
  • Title level requests - features and info
  • Kiwi Release - MARC Holdings capabilities
  • Create orders by importing MARC Bibliographic Records

...

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://wikifolio-org.folioatlassian.org/net 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 2.2 - KG made change
• MF / GG: High level descriptions don't include additional narrative to provide context. For example, "this is a long awaited feature" or "this feature is connected to the bug that was first reported at first date"

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)
• https://help.oclc.org/Discovery_and_Reference/WorldCat_Discovery/Release_notes/2022_release_notes/045WorldCat_Discovery_release_notes_November_2022  What I appreciate with the WCD release notes are the screenshots with notations showing exactly what's changing in the interface.  Obviously only useful for some things in a FOLIO release and a completely smaller scale than our FOLIO updates too; so many not be practical. 

...