Page Comparison

...

Product Owner: Rob Kaufman

Vital Statistics:

https://badge.fury.io/rb/bulkrax https://circleci.com/gh/samvera/bulkrax https://coveralls.io/github/samvera/bulkrax?branch=main

Requirements for a Core Component

...

Code: active_fedora

Product Owner: Tamsin Johnson

Vital Statistics:

[![Build Status](https://circleci.com/gh/samvera/active_fedora.svg?style=svg)](https://circleci.com/gh/samvera/active_fedora)

...

Woo

browse-everything

Code: browse-everything

Product Owner: James R. Griffin III

Vital Statistics:

...

hydra-derivatives

Code: hydra-derivatives

Product Owner: Stuart Kenny

Vital Statistics:

...

hydra-editor

Code: hydra-editor

Product Owner: James R. Griffin IIIVital Statistics:

...

hydra-file_characterization

...

Product Owner: Jamie Little

Vital Statistics:

hydra-head

Code: hydra-head

Product Owner: Chris Colvard

Vital Statistics:

hydra-pcdm

Code: hydra-pcdm

Product Owner: Mark BusseyVital Statistics:

hydra-role-management

Code: hydra-role-management

Product Owner: James R. Griffin IIIVital Statistics:

hydra-works

Code: hydra-works

Product Owner: Mark Bussey

Vital Statistics:

iiif_manifest

Code: iiif_manifest

Product Owner: Karen Shaw

Vital Statistics:

ldp

Code: ldp

Product Owner: Randall Floyd

Vital Statistics:

noid-rails

Code: noid-rails

Product Owner: Justin CoyneVital Statistics:

questioning_authority

Code: questioning_authority

Product Owner: James R. Griffin III

Vital Statistics:

rubydora

Code: rubydora

Product Owner: Justin CoyneVital Statistics:

http://samvera.github.io

Code: samvera.github.io

Product Owner: Andrew MyersVital Statistics:

valkyrie

Code: valkyrie

Product Owner: Alexandra Dunn

Technical Lead: Trey Pendragon

Vital Statistics:

...

bixby

Code: bixby

Product Owner: James R. Griffin IIIVital Statistics:

samvera-circleci-orb

Code: samvera-circleci-orb

...

Technical Lead: Collin BrittleVital Statistics:

Gem Release Process

1. Create a new branch of the following form: git checkout -b prepare-release-3.2.1 where 3 is the major release, 2 is the minor release, and 1 is the patch release (please see Semantic Versioning for reference).

2. Within this branch, please update the following:

3. Version number (this is often found within lib/[GEM_NAME]/version.rb)

4. The CHANGELOG.md

5. Any additional documentation and areas of code

6. Commit these changes (using git commit) and push these to the GitHub repository using git push origin prepare-release-3.2.1

7. Create a Pull Request and request a review from @samvera/maintenance

8. A member of the Component Maintenance Interest Group should approved of and merge the pull request

9. One this has been completed, there are now two tasks left (both can be delegated to members of @samvera/maintenance):

10. 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 RubyGems

11. As this creates a new git tag with the version as the tag name, this can be used to draft and publish a release on GitHub

12. Please 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.