diff options
| author | Andrew Hooker <geekoncoffee@gmail.com> | 2014-12-01 17:09:19 -0600 |
|---|---|---|
| committer | Andrew Hooker <geekoncoffee@gmail.com> | 2014-12-01 17:09:19 -0600 |
| commit | 197a8ec2721d2f58b7a30cd23a6cf38e524e3936 (patch) | |
| tree | 903fbb5205996a703e5afb9879c90e92ed4a8cd4 /DEVELOPMENT.md | |
| parent | ffa9ed77d28d5777c6cac3085d01e2fdfd226cad (diff) | |
| download | bundler-197a8ec2721d2f58b7a30cd23a6cf38e524e3936.tar.gz | |
Add comment about bundler-features repo
Make it more obvious that feature discussions should go on the bundler-feature repo
Diffstat (limited to 'DEVELOPMENT.md')
| -rw-r--r-- | DEVELOPMENT.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 365de702..3442ed88 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -70,7 +70,7 @@ Finally, the ticket may be a duplicate of another older ticket. If you notice a If you would like to add a new feature to Bundler, please follow these steps: - 1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) to discuss your feature. + 1. [Create an issue](https://github.com/bundler/bundler-features/issues/new) in the bundler-features repo to discuss your feature. 2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases. 3. Commit the code and at least one test covering your changes to a feature branch in your fork. 4. Put a line in the [CHANGELOG](https://github.com/bundler/bundler/blob/master/CHANGELOG.md) summarizing your changes under the next release under the "Features" heading. |