kotovalexarian-likes-github
/
sinatra
mirror of https://github.com/sinatra/sinatra
1
0
Fork 0
Code Releases Activity

update CHANGELOG and CONTRIBUTING.md 

The CHANGELOG entry will automatically be generated in the near future,
so we don't need to manually update it.
This commit is contained in:
Kunpei Sakai 2019-02-08 01:24:34 +09:00
parent 2e36823823
commit 6f15fba279
No known key found for this signature in database
GPG Key ID: C4B6919318C291BC
2 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -1,7 +1,3 @@
## Unreleased
* Avoid `TypeError` when params contain a key without a value on Ruby < 2.4 [#1516](https://github.com/sinatra/sinatra/pull/1516) by Samuel Giddins
## 2.0.5 / 2018-12-22
* Avoid FrozenError when params contains frozen value [#1506](https://github.com/sinatra/sinatra/pull/1506) by Kunpei Sakai

8
CONTRIBUTING.md
View File

@ -36,13 +36,7 @@ can be applied as quickly as possible:
modify the `README.md` file to reflect that. Again, if you don't
update the `README`, we have to, and this holds up acceptance.
4. **Update the change log (`CHANGELOG.md`):** The change log helps give an
overview of the changes that go into each release, and gives credit
where credit is due. We make sure that the change log is up to date
before each release, and we always appreciate it when people make
it easier to get the release out the door.
5. **Push it:** Once you're ready, push your changes to a topic branch
4. **Push it:** Once you're ready, push your changes to a topic branch
and add a note to the ticket with the URL to your branch. Or, say
something like, "you can find the patch on johndoe/foobranch". We also
gladly accept GitHub [pull requests](http://help.github.com/pull-requests/).