Was 4.0.3 taged/released correctly or did something go wrong?

From:
https://github.com/rails/rails/issues/12808#issuecomment-35476010

To be honest I think something went wrong when tagging v4.0.3.

$ git log --oneline v4.0.2..v4.0.3 | wc -l
3
$ git log --oneline v4.0.2..origin/4-0-stable | wc -l
266

v4.0.3 only contains three commits not found in v4.0.2

Jarl

4.0.3 is a security fix release:

http://weblog.rubyonrails.org/2014/2/18/Rails_3_2_17_4_0_3_and_4_1_0_beta2_have_been_released/

Chris

According to semantic versioning, this is perfectly normal.

Updating to a 4.0.x should be straight forward.

This was not respected when updating from 4.0.0 to 4.0.1, it was a real pain to update.

4.0.3 is a security update. To make it easy to apply security fixes, we try to make these security updates as minimal as possible.

The other bug fixes originally scheduled for 4.0.3 are pushed to 4.0.4.

Godfrey