From 3fc0538188a88fc41d7a16f245f728668b286389 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Thu, 4 Jun 2026 13:16:55 +0900 Subject: [PATCH 1/2] Point contributors to GitHub Discussions instead of the RFC repo The rubygems/rfcs repository is no longer maintained, so the feature request docs still sent people to a dead end. Route idea-stage proposals and large-change discussion to GitHub Discussions instead, and keep issues for changes whose direction is already settled or for problems that need fixing. Co-Authored-By: Claude Opus 4.8 (1M context) --- doc/NEW_FEATURES.md | 4 ++-- doc/POLICIES.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/NEW_FEATURES.md b/doc/NEW_FEATURES.md index f571ced62218..c9ae4a99baf0 100644 --- a/doc/NEW_FEATURES.md +++ b/doc/NEW_FEATURES.md @@ -2,13 +2,13 @@ ## Substantial Features -To request substantial changes to Bundler or Bundler documentation, please refer to the [RFC repository](https://github.com/rubygems/rfcs). See the [README](https://github.com/rubygems/rfcs/blob/master/README.md) for detailed instructions on the RFC process. +To request substantial changes to Bundler or Bundler documentation, please start a discussion in [GitHub Discussions](https://github.com/rubygems/rubygems/discussions). ## Contributing New Features To add a new feature to Bundler: -1. **Discuss your idea** - [Open an issue](https://github.com/ruby/rubygems/issues/new) to discuss your proposed feature +1. **Discuss your idea** - If the goal is already clear, link the existing [issue](https://github.com/rubygems/rubygems/issues) or [discussion](https://github.com/rubygems/rubygems/discussions) that covers it. Otherwise, post your idea in [GitHub Discussions](https://github.com/rubygems/rubygems/discussions) first so it can be talked through 2. **Base on master branch** - We follow [SemVer](https://semver.org), so new features go in the master branch only, not old releases 3. **Write tests** - Include at least one test covering your changes in your feature branch 4. **Submit a pull request** - See [PULL_REQUESTS.md](PULL_REQUESTS.md) for detailed guidelines diff --git a/doc/POLICIES.md b/doc/POLICIES.md index fecc3afbae1e..47f92ba020f3 100644 --- a/doc/POLICIES.md +++ b/doc/POLICIES.md @@ -93,9 +93,9 @@ avoid breaking things, and we may even intentionally introduce this kind of cases. So be aware when using internals and ideally get in touch with us before doing so, so that we can help find the right APIs. -## RFC guidelines +## Discussing large changes -Large changes often benefit from being written out more completely, read by others, and discussed. The [Bundler RFC repo](https://github.com/rubygems/rfcs) is the preferred place for that to happen. +Large changes often benefit from being written out more completely, read by others, and discussed. [GitHub Discussions](https://github.com/rubygems/rubygems/discussions) is the preferred place for that to happen. ## Committer Access From db38da864e78cbbcf25bb9611064b074b6baf29b Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Thu, 4 Jun 2026 13:17:06 +0900 Subject: [PATCH 2/2] Describe the rational versioning policy instead of SemVer RubyGems and Bundler do not follow SemVer strictly, so claiming we do was misleading. Spell out the actual policy: major may break existing code, minor can change behavior while keeping existing functionality working, and tiny is mostly bug fixes that may include small feature additions. Co-Authored-By: Claude Opus 4.8 (1M context) --- doc/NEW_FEATURES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/NEW_FEATURES.md b/doc/NEW_FEATURES.md index c9ae4a99baf0..9af24228781e 100644 --- a/doc/NEW_FEATURES.md +++ b/doc/NEW_FEATURES.md @@ -9,7 +9,7 @@ To request substantial changes to Bundler or Bundler documentation, please start To add a new feature to Bundler: 1. **Discuss your idea** - If the goal is already clear, link the existing [issue](https://github.com/rubygems/rubygems/issues) or [discussion](https://github.com/rubygems/rubygems/discussions) that covers it. Otherwise, post your idea in [GitHub Discussions](https://github.com/rubygems/rubygems/discussions) first so it can be talked through -2. **Base on master branch** - We follow [SemVer](https://semver.org), so new features go in the master branch only, not old releases +2. **Base on master branch** - Substantial new features go in the master branch only. Releases follow a rational versioning policy: major versions may break existing code, minor versions can change behavior or output while keeping existing functionality working, and tiny versions are mostly bug fixes that may include feature additions 3. **Write tests** - Include at least one test covering your changes in your feature branch 4. **Submit a pull request** - See [PULL_REQUESTS.md](PULL_REQUESTS.md) for detailed guidelines