Package upgrades in RHEL minor releases not being documented

Latest response

Hi,

I've noticed that between RHEL minor releases, packages are sometimes upgraded to new major upstream versions (as opposed to upstream maintenance releases / updates). However, these upgrades are not always being documented in either the technical notes or the release notes.

For example, xorg-x11-xserver (X.org Server) has been upgraded 3 times in RHEL 6.x minor releases:
1.7 (6.0) -> 1.10 (6.2) -> 1.13 (6.5) -> 1.15 (6.6)

While I greatly appreciate new hardware enablement and new features in X.org Server, I would expect to see these major version upgrades reflected in either the release notes or the technical notes.

The 1.10 upgrade was documented:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Release_Notes/graphics.html

But the 1.13 upgrade was not. It might be implied from the Release Notes that it was upgraded:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.5_Release_Notes/bh-chap-desktop_and_graphics.html
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.5_Technical_Notes/xorg-x11-server.html

And there is no sign of the 1.15 upgrade in the documentation:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.6_Release_Notes/bh-chap-desktop_and_graphics.html
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.6_Technical_Notes/index.html

My interest in this is two-fold.
1. In my free time, I contribute to the X2Go project, which is maintaining a fork of X.org called nx-libs. If a Linux distro is upgrading the X.org server, we want to know about it, because applications may assume that the linux distro's users have a much newer version of X.org server than nx-libs is based on.
2. At work, we may migrate to RHEL. When a package is upgraded to a new major version, we would presumably want to do extra regression testing of our code that uses that package.

Thanks,
-Mike

Responses

Hi Mike,

Usually our errata, and therefore also the technical notes, contain the following fixed phrase when we're rebasing a component:

"The $COMPONENT packages have been upgraded to upstream version $VERSION, which provides a number of bug fixes and enhancements over the previous version. (BZ#$BUGZILLA_WITH_REBASE_KEYWORD)"

You can see this text in the technical notes for RHEL 6.3, where the rebase to 1.13 took place: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.4_Technical_Notes/index.html#xorg-x11-server.

In 6.6 the situation was different mainly due to a major change in the way the X server was packaged: the rebase of the xorg-x11-server component was part of a large erratum containing various related changes. So the rebase itself might not have been prominent. Here's the text:

"Utilities and drivers contained in the xcb-util package have been upgraded to newer upstream versions to provide a number of fixes and enhancements. The following components have been upgraded: xorg-x11-server, ..." . See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.6_Technical_Notes/index.html#RHBA-2014-1376.

That said, it sounds like a good idea to make upgrades in RHEL X.Y visible at first sight. I'll pass your feedback to the team that works on release/technical notes.

Radek

Thanks.

It looks like the upgrade to 1.13 took place in RHEL 6.4, not 6.5 or 6.3. Sorry for the confusion.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.