Hi,

On Mar 12, 2008, at 01:39, Howard Johnson wrote:

> wolf2k5 wrote:
>> It looks like RH finally decided to bump up the base version of some
>> packages (e.g.mysql: 5.0.22-2.1.0.1 -> 5.0.45-6.el5) instead of
>> backporting fixes to the older base version.
>
> Note that it's a minor version bump, they're both 5.0.x versions.
> They did this before with mysql in RHEL4 (4.1.7 -> 4.1.10a -> 4.1.12
> -> 4.1.20). My guess is that it's a fairly special case; as I
> understand it, MySQL AB tend to be quite careful about their
> security and bug fixing (and not introducing major new features), so
> updating to a newer version in the same release train is likely
> easier than / as safe as backporting fixes.


In my opinion this isn't really true. MySQL has a record of
accidentally changing ABI between minor releases - sometimes
undocumented - and then reverting the change in for the next release;
see mysql bugs #21829, #23427 for example. Also a lot of features
receive "Incompatible change" mentions in their changelogs; whether
one of them affects you or not is random. ;-)

To end this message on a more positive tone upgrading between MySQL
versions is certainly easiler than with PostgreSQL (8.0 -> 8.1 -> 8.2 -
> 8.3 -> etc) ;-)




HTH

Kaj
--
Kaj J. Niemi
<kajtzu@(protected)>
+358 45 63 12000

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list