-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find "stable" branches which haven't been released #15
Comments
Cut a release if necessary. |
https://github.com/samvera/questioning_authority/tree/stable_1.2_for_rails_4.2 may be a release, but I don't see a 1.0.0 on https://rubygems.org/gems/questioning_authority |
https://github.com/samvera/hydra-head/tree/8-2-stable does not offer any significant changes following the release 8.2.0. |
https://github.com/samvera/hydra-head/tree/8-1-stable may require a release. |
https://github.com/samvera/hydra-head/tree/8.0-stable does not require a release. |
There was never a 6.6.0 release, but https://github.com/samvera/hydra-head/tree/6-6-stable offers some changes beyond 6.5.2 (which are not as severe as what was introduced in 7.0.0). |
There are no releases published prior to 3.3.0: https://rubygems.org/gems/noid-rails/versions |
There are no releases published prior to 3.3.0: https://rubygems.org/gems/noid-rails/versions |
https://github.com/samvera/hydra-pcdm/tree/0.9-stable is on par with release 0.9.0 |
https://github.com/samvera/active_fedora/tree/8.x-stable is tied to release 8.4.2 |
https://github.com/samvera/active_fedora/tree/11-2-stable relaxes the dependency upon |
https://github.com/samvera/active_fedora/tree/6-8-stable permits later releases of |
https://github.com/samvera/active_fedora/tree/10.2-stable is behind release 10.2.1 |
https://github.com/samvera/active_fedora/tree/6-7-stable has changes beyond release 6.7.8 |
https://github.com/samvera/active_fedora/tree/9.0-stable has changes beyond release 9.0.7 |
https://github.com/samvera/active_fedora/tree/6.5-stable has changes beyond release 6.5.1 |
https://github.com/samvera/hydra-works/tree/0.12-stable is on par with release 0.12.1 |
https://github.com/samvera/hydra-editor/tree/3-3-stable requires a new release for version 3.3.3 |
In order to address the possible releases, I have created the following: |
https://github.com/samvera/hydra-head/tree/3.0.x is at par with release 3.0.1. |
There are no releases tagged for 2.0.0 or published on RubyGems (regarding https://github.com/samvera/hydra-head/tree/2.x) |
https://github.com/samvera/active_fedora/tree/release-8.x is at par with release 8.7.0 |
https://github.com/samvera/active_fedora/tree/release-2.1.0 is erroneously tied to release 12.1.0: https://github.com/samvera/active_fedora/blob/release-2.1.0/lib/active_fedora/version.rb |
https://github.com/samvera/active_fedora/tree/5.x has changes beyond release 5.7.1 which may justify a new release. |
https://github.com/samvera/active_fedora/tree/3.3.x has changes beyond release 3.3.2 which may justify a new release. |
https://github.com/samvera/active_fedora/tree/3.2.x is at par with release 3.2.2, with the exception of one line of documentation:
|
https://github.com/samvera/active_fedora/tree/3.1.x is at par with release 3.1.6 |
https://github.com/samvera/active_fedora/tree/3.0.x is at par with release 3.0.7, with the exception of the following locked dependency:
|
https://github.com/samvera/active_fedora/tree/2.x is at par with release 2.3.8. |
After reviewing branches following the naming pattern of |
Many of these issues may refer to branches which are simply too old to justify new patch or minor releases. After having this brought to my attention by @jcoyne, it was made clear that it is still desirable to retain these older branches from the standpoint of maintaining the code base, and providing reference points for features and past bugs. It should also be noted that Rails does follow this practice: https://github.com/rails/rails/branches/all |
I will need to contact the product owners for the affected Gems and update this. |
Released hydra-editor 5.0.2 (don't seem to have access to check it off up top). |
Released |
The text was updated successfully, but these errors were encountered: