Page Comparison

Technical Council Sub Groups Updates

• TCR process:  still working with RMS, then some communication that may or may not wait for RMS
  
  • Existing modules: some criteria should apply, but current review process doesn't
  • Return to process after formalization
• Working on static code review subgroup, need to reach out to devs

Review the following language:

Hello FOLIO Developers!

The FOLIO Technical Council wants to ensure that we are engaging with topics that are relevant to the development efforts of our community. We feel that no group is more aware of what these topics are then the developers themselves. We would like to encourage you to share with us  suggestions for topics that that are impactful to the FOLIO development experience.

Please share any such topic suggestion with us in the #tech-council slack channel, and thank you for all the hard work!

___

• Jeremy will post for developers + slack channels

• Mine GH for evidence of breaking changes, ask teams to add labels to PRs
• see 2024-02-21 - Communicating Breaking Changes
• https://docs.google.com/spreadsheets/d/1jHfxvNQRnQuHeCcv0NlSc6eti0IHEyVTe4eO1q419gk/edit#gid=0
• https://github.com/folio-org/breaking-changes-notification-poc
• Once things are gathered what happens? Posts to slack channel where interested parties can watch for changes and see if they are affected.  Hoping summary in PR will let people know if they need to investigate further.
• Have release notes with breaking changes but those are too late.
• Try running the POC for a while and see how it goes. Need to make sure development community understands how to do the labels. Description is optional but useful. See if some set of teams thinks it is worthwhile and willing to try.
• Olamide: Things could get missed in the slack channel, knowing before the change is merged is most helpful.
• Any major version change should be accompanied with the label. A way to force agreement? Would we want to?
• How do teams currently signal?  Nothing formal. This is an attempt to provide the mechanism. Tech leads could be an option but that group didn't work so well. Is there a better way than slack to make people aware of breaking changes.
• Hard for TC to facilitate announcement before it is evidenced in code.  PR is the earliest can automatically scan for, anything else would require active participation from the dev teams to make announcements.
• Some kind of notification when the PR is created, if PR has the label, could make it happen earlier.
• Targeted to teams working on specific modules?
• Slack notifications can be used to let people to opt into their own announcements. Individuals can set up their own notifications
• People not attending them to later in the process, or not realizing they were breaking changes, leading to some scrambling
• Try with limited scope experience
• Use a Wednesday topic discussion and try to get folks already using the breaking change label to try this
• Can also give refresher link on definition of breaking changes
• At one point teams were responsible for creating PRs when they made breaking changes that affected other modules
• Make sure useful for development teams and sysops as well
• Jeremy will publicize upcoming discussion

Proposal: 

•  give feedback, have until end of the month

Officially Supported Technologies (OST)

Topic Backlog Grooming