Permalink
Browse files

Add info about placing a new CHANGELOG entry to contributing guide

  • Loading branch information...
1 parent 73bbf54 commit 4e211d3faca5e62a4a580c8b756c7479b62d0781 @drogus drogus committed Jul 22, 2013
Showing with 1 addition and 1 deletion.
  1. +1 −1 guides/source/contributing_to_ruby_on_rails.md
View
2 guides/source/contributing_to_ruby_on_rails.md
@@ -264,7 +264,7 @@ The CHANGELOG is an important part of every release. It keeps the list of change
You should add an entry to the CHANGELOG of the framework that you modified if you're adding or removing a feature, committing a bug fix or adding deprecation notices. Refactorings and documentation changes generally should not go to the CHANGELOG.
-A CHANGELOG entry should summarize what was changed and should end with author's name. You can use multiple lines if you need more space and you can attach code examples indented with 4 spaces. If a change is related to a specific issue, you should attach issue's number. Here is an example CHANGELOG entry:
+A CHANGELOG entry should summarize what was changed and should end with author's name and it should go on top of a CHANGELOG. You can use multiple lines if you need more space and you can attach code examples indented with 4 spaces. If a change is related to a specific issue, you should attach issue's number. Here is an example CHANGELOG entry:
```
* Summary of a change that briefly describes what was changed. You can use multiple

0 comments on commit 4e211d3

Please sign in to comment.