2026-01-13 Release Management & Commmunication WG meeting notes
Date
Jan 13, 2026
Participants
@Autumn Faulkner @Charlotte Whitt @Jennifer Eustis @Tod Olson @Thomas Trutt
Regrets: @Jeremy Huff
Guests: Khalilah, Christine, and Magda from the POs group
Agenda
Collaboration on release communications
@Khalilah Gambrell , @Christine Schultz , and @Magda Zacharska (Deactivated) joining us to compare notes
POs have similar plans to create a condensed version of release highlights
See examples here:Notes on functionality - BETA
Discussion points
Are we thinking of the same audience? I.e., FOLIO users at implementing libraries with little interest/time for technical details
POs aiming to reach users like people who use BulkEdit every day, want to know what’s new, no system responsibilities, don’t need the more technical info
Organized by app
Each report includes new features, enhancements, bug fixes (uses Jira filter), further info (link to more details)
Our group views the RMS release digest as communication for a separate audience, with a different purpose. Would POs agree?
We forgot to ask this specifically but this is an inferred yes – release digest serves it’s own purpose.
If we want to combine efforts, how should the process work?
If POs create the content for each app, PC can contribute via:
Reviewing first drafts for each release, providing suggestions
Distributing to identified channels
FOLIO project LinkedIn account (email @Hannah Murphy (Deactivated))
Newsletters (PC, OLF, perhaps hosting provider updates)
Self-hosted institutions' Slack channel
docs.folio.org (need to check on this with Docs WG)
Further ideas:
Revamp the standard format of the wiki release notes page to group information by user role
Developers and sysadmins → Oleksii’s full release digest
General users → abbreviated notes on functionality
Sprint demos?
Perhaps some customized content for team managers?
More specific info is sometimes needed
Example: what set-for-deletion limitations are
Folio.org content
Hannah may be able to contextualize the standard link to the release notes wiki page by adding a brief description – she will check and inform the group
By adjusting the wiki landing page, we can better direct any traffic coming from folio.org
Get some user feedback
Christine and Magda posted in Implementers Slack and didn’t get a big response
Magda would like to hear from the folks who aren’t necessarily involved in SIGs, just sitting in their libraries trying to learn new functionality. How do we reach these users?
Action items
RMC WG members -- review current beta versions and send suggestions to POsNext meeting (1/20)