Issue #15605 has been updated by headius (Charles Nutter).


> Perhaps a better general solution may be to allow the ruby main team to decide who is co-owner of gems IF these gems are part of the official ruby distribution.

This seems like a good rule of thumb. I know we've had trouble finding maintainers for some libraries, but anything that lives as an external gem should have at least two maintainers always in case one gets pulled away. The json gem has for too long had only the one maintainer, other than partial support from JRuby team for our version of the extension.

> You may know hsbt and I get write access to repo recently.

That's great! We'll ping you from the relevant PRs we need merged and we can talk about a release.

I'm not sure whether I can (or should) add naruse or hsbt as a gem pusher...but I think we need someone (other than flori) from the C side to also be able to push the gem when there's fixes.

> Would it make sense to move the repository under the ruby organization, since it is a default gem maintained by ruby-core now?

I think it would be worthwhile to do this for every gem that's included as part of stdlib. The racc library has similar issues, not because of unresponsive maintainers but because nobody really wants to own it anymore. I've been trying to get some fixes in there and released too (working with tenderlove on and off this month to do that).

----------------------------------------
Bug #15605: json library needs more frequent releases
https://bugs.ruby-lang.org/issues/15605#change-76864

* Author: headius (Charles Nutter)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: all
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
There has not been a release of the json gem since April 2017.

Unfortunately there's a long backlog of bugs and pull requests that have been sitting there, including some that prevent users from upgrading JRuby.

I think most of us who have been working on Ruby for any length of time knows that it has been difficult to get json changes released, and it's now starting to really hold back other development.

I propose that we start looking for an alternative maintainer of the library, find a way to get them push rights, and end this bottleneck.

FWIW only flori and I currently have push rights for the gem, but I do not have push rights for the repository.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>