README.md in best_boy-3.0.0 vs README.md in best_boy-3.1.0

@@ -11,28 +11,13 @@
 
 
 Rails version support
 ----------------------
 
-BestBoy 3 and above only supports Rails >= 4.1
+BestBoy 3 and above only supports Rails >= 4.2
 
 
-Changes in version 3
-----------------------
-
-Best Boy version 3 comes with some backward incompatible changes. However, it's totally worth it because BestBoy now follows all the best practices of a rails engine.
-This and additional changes of version 3 include
-
-* Uses rails engine naming conventions with an isolated ``BestBoy`` namespace
-* serving the necessary migrations from the engines migration folder
-* serving all assets via the asset pipeline (used to be a opt-in before)
-* removes unnecessary generator boilerplate and config options
-* uses the newest Bootstrap version (3)
-* allows per class extending instead of polluting the whole app
-* answers to xml requests for easy EXCEL integration
-
-
 Installation
 ------------
 
 Add it to your gemfile
 
@@ -147,12 +132,26 @@
 Budget some time for this task, since it can take long if your BestBoyEvent table has grown very big.
 
 
 Changelog
 ---------
+#### HEAD (not released yet)
+
+#### 3.1.0
+* Drop support for Rails 4.1
+* Add support for Rails 5.0
+
 #### 3.0.0
 * Major engine cleanup. Aims Rails >= 4.1 from now on.
 * Includes backward incompatible changes. See above hint for more information.
+* Uses rails engine naming conventions with an isolated ``BestBoy`` namespace
+* serving the necessary migrations from the engines migration folder
+* serving all assets via the asset pipeline (used to be an opt-in before)
+* removes unnecessary generator boilerplate and config options
+* uses Bootstrap 3
+* allows per class extending instead of polluting the whole app
+* answers to xml requests for easy EXCEL integration
+
 
 #### 2.2.3
 * Rename ``report`` method to a more best_boy specific ``trigger_best_boy_event_report`
 
 #### 2.2.2