...

While there is not a single, consistent Gem release process for every Core Component, there are a number of common patterns used to simplify the tasks involved. The most common includes the usage of a Rake command `rake release`, which automates the process of generating a new `git` tag for the release, as well as building and publishing the new release to RubyGems. One case is very well documented on https://github.com/samvera/active_fedora/wiki/Release-management-process.

Backlog Management

Another responsibility of the Product Owner to address for a Core Component is the management of the issue backlog for the GitHub project. The manner by which one is to create and track GitHub issues has been left entirely to the discretion of each Product Owner. However, it is quite common to use a GitHub Project Board (please find an example at the following: https://github.com/samvera/valkyrie/projects/2) in order to best organize issues to be addressed by community members or the Working Group during a sprint. Further, it may also be valuable to attempt to explore the usage of GitHub issue labels (https://help.github.com/en/github/managing-your-work-on-github/about-labels), and GitHub milestones (https://help.github.com/en/github/managing-your-work-on-github/about-milestones) in order to more easily organize issues as they relate to any planned releases for a Gem.