May 2022 Monthly Update
ruby together news
In May, Ruby Together was supported by 36 different companies, including Ruby member Zendesk. On top of that we were supported by 133 developer members. Thanks to all of our members for making everything that we do possible. <3
The following is a non-exhaustive list of other improvements included in the above releases (see the changelog for further information):
- fixed a regression causing an error message when an incompatible Ruby version is used - #5525.
- fixed an issue with inline mode install output printing information about previously locked gems - #5529, #5530.
- fixed a regression when printing resolution conflicts on metadata requirements - #3362.
- refactored the code that handles finding a target version in
gem update --system- #5568.
- made an update to display better error messaging when previous installation fails to be removed -#5664.
- improved exception reporting in bug report template - #5563.
In May, RubyGems gained 84 new commits, contributed by 9 authors. There were 851 additions and 472 deletions across 123 files.
In May, RubyGems.org saw several bug fixes and updates, some of which include the following:
- fixed access to undefined variable version in
- fixed some lint failure issues - #3069.
- set UTC date format in
update_version_file_testrake task - #3066.
- re-designed dependencies list on RubyGems UI - #3062.
- added a fix to find versions explicitly by name & platform - #3060.
This month, RubyGems.org gained 51 new commits, contributed by 15 authors. There were 580 additions and 91 deletions across 35 files.
In May we completed 56 hours of development work @$150/hour, and spent $8,398.50.
Until next time,
Irene, André, and the Ruby Together team
June 23, 2022