To view parent comment, click here.
To read all comments associated with this story, please click here.
This is the first time I've heard an Enterprise customer complain about a lack (?!?!?) of major version changes.
RedHat decided that they rather re-base major changes (KVM, FF3, Evolution, kernel driver upgrades, etc) and delay RHEL 6 until it's ready.
As someone that ships proprietary software around RHEL, I can only agree.
- Gilboa
I agree that that's a long time, but in Redhat's defense, that is an issue with the desktop chosen, not RHEL itself. GNOME is a dependency nightmare, but thats part of what make it work the way it does, its got its hooks fairly deep into the core of the system. Problem is that there is a point where it ceases to just be a gui overlay.
In contrast, if you were running KDE,XFCE,Fluxbox, etc...you could freely move between desktops with very little dependency on the core. KDE-Redhat group releases new builds regular of KDE, but its not to difficult to compile.
When it comes to the desktop, let put blame where it belongs, and that's the desktop project. GNOME, as much as i like it, has always had this issue, it is virtually impossible to change the version of gnome on a system, without upgrading pretty much everything thats not a server process lol. KDE is MUCH better in this regard, not being to picky about the underlying OS, but KDE4 has been a bit of a disaster thus far.
Pick your poison..
I disagree. Because the core problem is that Red Hat made very explicit promises to its customers, and then just arbitrarily broke them because it worked out better for their business model. Sounds like that same thing we point fingers at proprietary vendors for doing. If they had announced, ahead of the 5.0 release that "Hey, we're going to go longer on the 6.0 release cycle", that would be one thing. But they didn't. Last I looked, which was not long ago, that same promise was *still* in their sales literature for RHEL5.[1] My customer would *not* have chosen RHEL if they had known what Red Had was going to unilaterally decide to do, for their own business reasons.
[1] http://www.redhat.com/f/pdf/rhel/rhel5_overview.pdf
Edited 2009-07-02 14:45 UTC






Member since:
2005-07-24
What's most annoying is that after including an 18 to 24 month release cycle promise in their sales material for every release from 2.1 through 5.something, Red Hat decided to simply ignore that promise, without so much as an explanation and/or apology. At 18 to 24 months between major releases, RHEL makes a decent XDMCP/NX server. But now, midstream, they say "Oh, it's going to be more like 36 months this time. That works out better for *our* business needs.".
Some parts are not so difficult to update from third party sources. Like OO.o. But how about Evince? Updating it to a later version is a source code dependency nightmare. Important business PDF documents which I know open just fine in later versions of Evince, fail to open for my users. And we were supposed to have had an upgrade path by last March.
Edited 2009-07-01 20:36 UTC