I guess my point was...why didn't they just give us 4.3.1?
It involves a lot more work (and time) to do an entire baseline upgrade, rather than backporting fixes into "known good" code. That's why a lot of Cobalt apps appear out of date and trip low-quality vulnerability scanners that just check an RPM version, etc.
Not saying I agree with the "policy" -- I'd like to see everything kept as up-to-date as is reasonably possible -- but at least I understand why they do what they do.
What would be "perfect" is if the download page and/or BlueLinQ info screen contained an actual changelog instead of just saying "upgrades PHP"... that way you could look and see "it _says_ 4.0.6 but it's equivalent in updates (note - that's different from functionality!) to a new 4.3.1 install"
-- bruce