...
[bulkrax is not a core component but is now promoted out of Samvera-labs to Samvera and should be listed with product owner.]
bulkrax
Code: bulkrax
Product Owner: Rob Kaufman
...
Please note that Hyrax is not considered a ‘component’ under the definition used by the CCMWG.
active_fedora
Code: active_fedora
Product Owner: Tamsin Johnson
...
Code:
browse-everything
Product Owner: James R. Griffin III
hydra-derivatives
Code: hydra-derivatives
Product Owner: Stuart Kenny
...
Code:
hydra-editor
Product Owner: James R. Griffin III
hydra-file_characterization
Code: hydra-file_characterization
Product Owner: Jamie Little
...
Code:
hydra-head
Product Owner: Chris Colvard
hydra-pcdm
Code: hydra-pcdm
Product Owner: vacant
...
Code:
hydra-role-management
Product Owner: James R. Griffin III
hydra-works
Code: hydra-works
Product Owner: vacant
...
Code:
iiif_manifest
Product Owner: Karen Shaw
ldp
Code: ldp
Product Owner: Randall Floyd
noid-rails
...
noid-rails
Product Owner: Justin Coyne
questioning_authority
Code: questioning_authority
Product Owner: James R. Griffin III
rubydora
Code: rubydora
Product Owner: Justin Coyne
...
Code:
valkyrie
Product Owner: Alexandra Dunn
Technical Lead: Trey Pendragon
bixby
Code: bixby
Product Owner: James R. Griffin III
samvera-circleci-orb
...
samvera-circleci-orb
Product Owner: James R. Griffin III
...
Create a new branch of the following form:
git checkout -b prepare-release-3.2.1
where3
is the major release,2
is the minor release, and1
is the patch release (please see Semantic Versioning for reference).Within this branch, please update the following:
Version number (this is often found within
lib/[GEM_NAME]/version.rb
)The CHANGELOG.md
Any additional documentation and areas of code
Commit these changes (using
git commit
) and push these to the GitHub repository usinggit push origin prepare-release-3.2.1
Create a Pull Request and request a review from
@samvera/maintenance
A member of the Component Maintenance Interest Group should approved of and merge the pull request
One this has been completed, there are now two tasks left (both can be delegated to members of
@samvera/maintenance
):The new Gem release can be published to RubyGems 1. Invoke
bundle exec rake release
1. This requires that one have an account with the necessary privileges on RubyGemsAs this creates a new
git tag
with the version as the tag name, this can be used to draft and publish a release on GitHubPlease notify any member of the Component Maintenance Interest Group, and we can assist by announcing the new release to the
#devs
Samvera Slack Channel and the samvera-tech Google Group.