From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:96424] [Ruby master Feature#15605] json library needs more frequent releases
Date: Mon, 23 Dec 2019 11:15:33 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-83346.20191223111533.75dba4393ef89bdf@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15605.20190215014056@ruby-lang.org
Issue #15605 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Assigned to Closed
naruse did release json-2.3.0 from the current master branch of ruby/ruby.
We will handle the new feature of JSON with ruby/ruby repo in the future.
----------------------------------------
Feature #15605: json library needs more frequent releases
https://bugs.ruby-lang.org/issues/15605#change-83346
* Author: headius (Charles Nutter)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version:
----------------------------------------
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/
next prev parent reply other threads:[~2019-12-23 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15605.20190215014056@ruby-lang.org>
2019-02-15 1:40 ` [ruby-core:91550] [Ruby trunk Bug#15605] json library needs a more responsive maintainer headius
2019-02-15 1:43 ` [ruby-core:91551] " headius
2019-02-15 1:45 ` [ruby-core:91552] " headius
2019-02-15 11:35 ` [ruby-core:91565] [Ruby trunk Bug#15605] json library needs more frequent releases shevegen
2019-02-17 1:08 ` [ruby-core:91577] " naruse
2019-02-17 11:18 ` [ruby-core:91579] " eregontp
2019-02-21 15:28 ` [ruby-core:91602] " headius
2019-03-13 13:21 ` [ruby-core:91808] " headius
2019-11-27 11:43 ` [ruby-core:95978] [Ruby master Feature#15605] " hsbt
2019-12-09 21:18 ` [ruby-core:96175] " headius
2019-12-23 11:15 ` hsbt [this message]
2019-12-23 12:56 ` [ruby-core:96428] " eregontp
2019-12-24 6:56 ` [ruby-core:96451] " hsbt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-83346.20191223111533.75dba4393ef89bdf@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).