Red Hat Enterprise Linux Life Cycle (Phases 1 - 3): http://www.redhat.com/security/updates/errata/
Most specifically ... With the increased development time for the next release, Red Hat announced the extension of "Phase 1" for Red Hat Enterprise Linux (EL) release 4 (EL4) and 5 (EL5) to four (4) years some time ago. Phase 1 still allows feature enhancements. So, at this time, EL5 is still considered Phase 1 (until 2011). Please utilize your support options, agreements and related avenues with Red Hat for EL5 considerations. Backporting Security Fixes (isolating changes and mitigating risk): http://www.redhat.com/security/updates/backporting/ Red Hat Enterprise Linux Updates (Release and other Notes): http://www.redhat.com/security/updates/notes/ Most specifically ... In-place upgrades of EL major version (X in XuY/X.Y) upgrades are technically supported by the Anaconda software. But as various release notes clarify, re-clarify and attempt to explain in various details, only EL "update" or "point release" minor version (Y in XuY/X.Y) upgrades may be supported by Red Hat for your subscription, agreement or other consideration. Major versions rebase software, which can have unforseen changes that cannot always be handled by Anaconda. When in doubt, contact your Red Hat representative, as they exist to serve you. ;) Also take advantage of Red Hat questionnaire, surveys and other customer feedback avenues to provide Red Hat with necessary directions for product development that best match customer needs. Furthermore, feature requests can always be made via Bugzilla by anyone in the community. Just be sure to understand the aforementioned lifecycle so they can be considered. Always be sure to search for existing requests to either add input as every input will go a long way to shaping engineering considerations (possibly even a concurrent "Tech Preview" version), or understand engineering considerations why enhancements and/or rebases cannot be considered. E.g., DNSSEC is in EL5 BIND, however, some features are supported by not feature complete due to mutually exclusive changes between BIND releases that would assuredly break existing configurations: https://bugzilla.redhat.com/show_bug.cgi?id=504052 https://bugzilla.redhat.com/show_bug.cgi?id=504794 -- Bryan "providing peer information and not speaking for any entity" P.S. As always, Red Hat Solutions Architects (SA), Technical Account Managers (TAM) and Consultants are additional resources separate from Red Hat Engineering regarding your business requirements and related considerations outside of normal product release, engineering and support -- while providing a direct avenue into these same engineering details. Always feel free to talk to your Red Hat representative about speaking to a SA about your needs, even if you are not interested in taking advantage of other support services at this time. They can provide additional insight for your future planning. -- Bryan J Smith Senior Consultant Red Hat, Inc Professional Consulting http://www.redhat.com/consulting mailto:[email protected] +1 (407) 489-7013 (Mobile) mailto:[email protected] (Blackberry/Red Hat-External) -------------------------------------------------------- You already know Red Hat as the entity dedicated to 100% no-IP-strings-attached, community software development. But do you know where CIOs rate Red Hat versus other software and services firms for their own, direct needs, year after year? http://www.redhat.com/promo/vendor/ _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
