Page Comparison

...

[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.

...

Code:

active_fedora

Product Owner: Tamsin Johnson

browse-everything

Code: browse-everything

Product Owner: James R. Griffin III

hydra-derivatives

Code: hydra-derivatives

Product Owner: Stuart Kenny

hydra-editor

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

...

Code:

hydra-works

Product Owner: vacant

iiif_manifest

Code: iiif_manifest

Product Owner: Karen Shaw

ldp

Code: ldp

Product Owner: Randall Floyd

noid-rails

Code: 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

...

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.