4 ms·
There have been other commits that made it into the 3-2-stable branch, and I would have expected that those fixes would have made it into the next 3.2.x release
by bratsche 14y ago
There have been other commits that made it into the 3-2-stable branch, and I would have expected that those fixes would have made it into the next 3.2.x release, but that's not the case. Is that normal for Rails updates?
For example, https://github.com/rails/rails/pull/8718 https://github.com/rails/rails/pull/8718 is a PR that was merged into 3-2-stable to deal with a regression in 3.2.8.
- steveklabnik 14y agoIt is my understanding that security updates are generally made by taking the last released version, applying the security patches, releasing, and then applying the patches to the end of 3-2-stable. This makes it incredibly easy for people to upgrade, and minimizes chances of regressions. The next non-security release of 3.2.x should include that change.
- bratsche 14y agoCool, thanks for the clarification Steve.