From: naruse@airemix.jp
To: ruby-core@ruby-lang.org
Subject: [ruby-core:101695] [Ruby master Bug#17468] Deprecate RUBY_DEVEL
Date: Fri, 25 Dec 2020 09:32:51 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-17468.20201225093250.5@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17468.20201225093250.5@ruby-lang.org
Issue #17468 has been reported by naruse (Yui NARUSE).
----------------------------------------
Bug #17468: Deprecate RUBY_DEVEL
https://bugs.ruby-lang.org/issues/17468
* Author: naruse (Yui NARUSE)
* Status: Open
* Priority: Normal
* Target version: 3.1
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Some configuration of Ruby use RUBY_DEVEL, which depends PATCH_LEVEL.
But depending PATCH_LEVEL causes issues which will become revealed on the final release.
Though we release some previews and RCs, they don't contributes the quality around RUBY_DEVEL.
Therefore to ensure CI tests the quality of the final release, we need to deprecate RUBY_DEVEL.
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2020-12-25 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 9:32 naruse [this message]
2021-10-19 21:29 ` [ruby-core:105683] [Ruby master Feature#17468] Deprecate RUBY_DEVEL jeremyevans0 (Jeremy Evans)
2021-12-25 7:45 ` [ruby-core:106819] " mame (Yusuke Endoh)
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.issue-17468.20201225093250.5@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).