ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: marcandre-ruby-core@marc-andre.ca
To: ruby-core@ruby-lang.org
Subject: [ruby-core:103930] [Ruby master Feature#17873] Update of default gems in Ruby 3.1
Date: Fri, 21 May 2021 04:34:57 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-92060.20210521043457.572@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17873.20210520104525.572@ruby-lang.org

Issue #17873 has been updated by marcandre (Marc-Andre Lafortune).


Thanks, I agree about `prime`.

I imagine `matrix` users are limited and will be ok. I'm not sure about `ostruct`.

Could we consider to bundle them in next major version but with some warning? If you "update" the gem then the conversion warning would not be there. This could ease conversion.



----------------------------------------
Feature #17873: Update of default gems in Ruby 3.1
https://bugs.ruby-lang.org/issues/17873#change-92060

* Author: hsbt (Hiroshi SHIBATA)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
I promoted many standard libraries to the default gems. You can see them at https://stdgems.org/#default-gems-ruby-301

I propose the following libraries to promote the bundled gems from the default gems.

```
ostruct: 
matrix
net/smtp
net/ftp
net/pop
net/imap
prime
```

They have primary maintainer in the canonical repository in github. So, they can release the new version with their convenience. 

@shugo @marcandre Any thought?

And I also propose to extract the following libraries from the default gems.

```
tracer
syslog
```

They are no longer actively maintained and not widely used today.




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

  parent reply	other threads:[~2021-05-21  4:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 10:45 [ruby-core:103912] [Ruby master Bug#17873] Update of default gems in Ruby 3.1 hsbt
2021-05-20 11:01 ` [ruby-core:103914] [Ruby master Feature#17873] " eregontp
2021-05-20 11:18 ` [ruby-core:103915] " hsbt
2021-05-20 12:24 ` [ruby-core:103918] " jean.boussier
2021-05-20 12:33 ` [ruby-core:103919] " hsbt
2021-05-20 15:17 ` [ruby-core:103920] " universato
2021-05-21  4:06 ` [ruby-core:103928] " hsbt
2021-05-21  4:34 ` marcandre-ruby-core [this message]
2021-05-21  5:39 ` [ruby-core:103935] " shugo
2021-05-21  9:05 ` [ruby-core:103944] " hsbt
2021-05-21  9:24 ` [ruby-core:103945] " hsbt
2021-05-21 10:12 ` [ruby-core:103947] " knu
2021-05-24  9:18 ` [ruby-core:104005] " hsbt
2021-05-27  5:43 ` [ruby-core:104059] " hsbt
2021-05-28  7:39 ` [ruby-core:104077] " jean.boussier
2021-05-28  9:56 ` [ruby-core:104080] " jean.boussier
2021-05-28 10:24 ` [ruby-core:104081] " deivid.rodriguez
2021-05-28 12:03 ` [ruby-core:104082] " jean.boussier
2021-05-28 12:05 ` [ruby-core:104083] " deivid.rodriguez
2021-05-28 18:25 ` [ruby-core:104086] " marcandre-ruby-core
2021-07-06 12:38 ` [ruby-core:104517] " eregontp
2021-07-06 16:50 ` [ruby-core:104521] " deivid.rodriguez
2021-07-07  8:32 ` [ruby-core:104528] " jean.boussier
2021-07-07 10:06 ` [ruby-core:104529] " deivid.rodriguez
2021-07-07 11:23 ` [ruby-core:104530] " jean.boussier
2021-07-07 11:44 ` [ruby-core:104531] " deivid.rodriguez
2021-07-07 11:53 ` [ruby-core:104532] " eregontp
2021-07-07 12:12 ` [ruby-core:104533] " deivid.rodriguez
2021-07-07 14:31 ` [ruby-core:104534] " jean.boussier
2021-07-07 17:34 ` [ruby-core:104536] " deivid.rodriguez
2021-07-08 10:40 ` [ruby-core:104543] " deivid.rodriguez
2021-10-15 10:32 ` [ruby-core:105641] " byroot (Jean Boussier)
2021-10-21 12:31 ` [ruby-core:105732] " hsbt (Hiroshi SHIBATA)
2021-10-22  0:28 ` [ruby-core:105745] " kou (Kouhei Sutou)
2021-10-23 20:58 ` [ruby-core:105759] " kou (Kouhei Sutou)
2021-12-27  5:42 ` [ruby-core:106832] " hsbt (Hiroshi SHIBATA)
2022-02-01 14:17 ` [ruby-core:107413] " Eregon (Benoit Daloze)
2022-02-01 14:20 ` [ruby-core:107414] " retro

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-92060.20210521043457.572@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).