CHANGELOG.md in bigbluebutton_rails-2.0.0 vs CHANGELOG.md in bigbluebutton_rails-2.1.0

@@ -1,7 +1,27 @@
 # Change Log
 
+
+## [2.1.0] - 2016-07-22
+
+* [#98] Improved how meeting records are created and ended. Now they are more reliable and
+  will work even if the resque workers are not running.
+* [#132] Fixed recordings being set as unavailable when making requests to a subset of the
+  recordings (when using filters in `getRecordings`).
+* [#133] Added option for applications to pass custom metadata when a meeting is being
+  created without having to create these metadata in the database.
+* Renamed the attributes `BigbluebuttonServer#salt` to `BigbluebuttonServer#secret`.
+
+
+------------------------------------
+
+All tickets below use references to IDs in our old issue tracking system.
+To find them, search for their description or ID in the new issue tracker.
+
+------------------------------------
+
+
 ## [2.0.0] - 2016-04-07
 
 To learn how to migrate to 2.0.0 see:
 https://github.com/mconf/bigbluebutton_rails/wiki/Migrate-to-2.0.0
 
@@ -244,9 +264,10 @@
 * First version
 * DB models for BigBlueButton servers and rooms
 * Controller to access servers and rooms
 * rooms_controller interacts with a BBB server using bigbluebutton-api-ruby
 
+[2.1.0]: https://github.com/mconf/bigbluebutton_rails/compare/v2.0.0...v2.1.0
 [2.0.0]: https://github.com/mconf/bigbluebutton_rails/compare/v1.4.0...v2.0.0
 [1.4.0]: https://github.com/mconf/bigbluebutton_rails/compare/v1.3.0...v1.4.0
 [1.3.0]: https://github.com/mconf/bigbluebutton_rails/compare/v1.2.0...v1.3.0
 [1.2.0]: https://github.com/mconf/bigbluebutton_rails/compare/v1.1.0...v1.2.0
 [1.1.0]: https://github.com/mconf/bigbluebutton_rails/compare/v1.0.0...v1.1.0