On 09/01/2014 04:50 AM, Markus Wildbolz wrote: > I just wanted to ask, why the commit > '1d0b91823db7856be3727fd351a3d7d3d5a9a2c5' from the git-repo isn't > included in the current stable 4.2.6 release?!?
The branch with that commit was written in 2014-04-15, but wasn't reviewed and merged into 4.2-trunk until 2014-07-16. By then the first release candidate for 4.2.6 had already been released (on 2014-07-07). As we don't change what is in the official release from the release candidate, the newly-merged branch was not included when the final release was made on 2014-07-16. The change is in 4.2-trunk, and will be in the next release, 4.2.7, which I expect to have a release candidate sometime this week. - Alex -- RT Training - Boston, September 9-10 http://bestpractical.com/training
