Update contribution docs#9594
Merged
Merged
Conversation
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) <noreply@anthropic.com>
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) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates contributor-facing documentation to reflect the move away from the separate RFC repository and to clarify how large changes should be discussed and how feature work should be proposed.
Changes:
- Replaces references to the Bundler RFC repo with guidance to use GitHub Discussions for large/substantial changes.
- Updates the Bundler feature request instructions to reference Discussions and adjusts release/versioning guidance text.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| doc/POLICIES.md | Replaces “RFC guidelines” section with guidance to discuss large changes via GitHub Discussions. |
| doc/NEW_FEATURES.md | Updates substantial feature request process and contribution steps, including discussion and release/versioning guidance. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## 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. |
| ## 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). |
|
|
||
| 1. **Discuss your idea** - [Open an issue](https://github.com/ruby/rubygems/issues/new) to discuss your proposed feature | ||
| 2. **Base on master branch** - We follow [SemVer](https://semver.org), so new features go in the master branch only, not old releases | ||
| 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 |
| 1. **Discuss your idea** - [Open an issue](https://github.com/ruby/rubygems/issues/new) to discuss your proposed feature | ||
| 2. **Base on master branch** - We follow [SemVer](https://semver.org), so new features go in the master branch only, not old releases | ||
| 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** - 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was the end-user or developer problem that led to this PR?
We no longer use RFCs repo and follow strict SemVer policy.
Make sure the following tasks are checked