Add RubyGems January Update #73
Conversation
|
|
||
| We also made the following improvements and fixes: | ||
|
|
||
| - looked up information for a CI related issue where the the `--silent` flag did not work with `gem update --system` - [#2907](https://github.com/rubygems/rubygems/issues/2907#issuecomment-756957235) and that was resolved on [#3789](https://github.com/rubygems/rubygems/pull/3789) |
There was a problem hiding this comment.
This bullet point doesn't seem important enough to me, specially since it didn't lead to any changes in rubygems. I'd unify this kind of change under a generic entry, like. "As always, we keep triaging new issues and reviewing pull requests from contributors".
There was a problem hiding this comment.
Alright noted will update this.
|
|
||
| - looked up information for a CI related issue where the the `--silent` flag did not work with `gem update --system` - [#2907](https://github.com/rubygems/rubygems/issues/2907#issuecomment-756957235) and that was resolved on [#3789](https://github.com/rubygems/rubygems/pull/3789) | ||
| - worked on RFC for Bundler Version Locking -[#29](https://github.com/rubygems/rfcs/pull/29). | ||
| - got pending releases out and kept working on more performance issues in bundler. |
There was a problem hiding this comment.
This is essentially duplicated with first sentence of this paragraph, but I think it's my note for the first two weeks of the month, when we released bundler 2.2.5 and bundler 2.2.6, and rubygems 3.2.5 and rubygems 3.2.6. I think it's probably worth unifying them.
| We also made the following improvements and fixes: | ||
|
|
||
| - looked up information for a CI related issue where the the `--silent` flag did not work with `gem update --system` - [#2907](https://github.com/rubygems/rubygems/issues/2907#issuecomment-756957235) and that was resolved on [#3789](https://github.com/rubygems/rubygems/pull/3789) | ||
| - worked on RFC for Bundler Version Locking -[#29](https://github.com/rubygems/rfcs/pull/29). |
There was a problem hiding this comment.
Here I'd say:
We keep refining our RFC for Bundler Version Locking (#29) and plan to move on to the implementation soon.
|
|
||
| ## RubyGems News | ||
|
|
||
| In January, we released new versions of bundler `v2.2.7` and `v2.2.8`, and rubygems `v3.2.7` and `v3.2.8`, the most important change being to fix resolver edge cases and speed up bundler - [#4277](https://github.com/rubygems/rubygems/pull/4277). This change makes bundler faster and the resolver more correct. We also keep refining our RFC for Bundler Version Locking -[#29](https://github.com/rubygems/rfcs/pull/29) and plan to move on to the implementation soon. |
There was a problem hiding this comment.
We also released bundler v2.2.5 and v2.2.6 in January (and corresponding versions of rubygems v3.2.5 and v3.2.6). We should mention all versions we released, and we can probablt say something like this to describe them in general instead of mentioning rubygems/rubygems#4277 specifically:
The main improvements in these releases are resolver correctness and better performance. Have a look a the changelogs for the specific changes: https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#328--2021-02-02 and https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#228-february-2-2021.
There was a problem hiding this comment.
alright, will update this part.
There was a problem hiding this comment.
The version numbers are different from what I added though is this in addition to the v2.2.7, v2.2.8 release?
There was a problem hiding this comment.
Yes, we released all 4 versions this month. You can check this in this page: https://rubygems.org/gems/bundler/versions (the rubygems versions are released the same day in sync, they're just 3.2.x, instead of 2.2.x).
There was a problem hiding this comment.
This is more accurate then.
In January, we released new versions of Bundler
v2.2.5,v2.2.6,v2.2.7, andv2.2.8, and corresponding versions of RubyGemsv3.2.5,v3.2.6,v3.2.7, andv3.2.8. The main improvements in these releases are resolver correctness and better performance. Learn more about specific changes made from the changelogs: Bundler Changelog and RubyGems Changelog.
There was a problem hiding this comment.
Yes, that looks perfect to me!
lauragift21
force-pushed
the
jan-2021-update
branch
from
4e2e2a8 to
6cdc031
Compare
Add RubyGems January 2021 Updates.
Hi, @deivid-rodriguez and @sonalkr132 can you help review to ensure I covered work done in January. Thanks!