Bug 82341
| Summary: | New Request:RFE: Quaterly update of errata | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Narsi Subramanian <narsis> |
| Component: | RHN/Other | Assignee: | Mike Orazi <morazi> |
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Network Quality Assurance <rhn-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | RHN Stable | CC: | acarter, bfaustyn, bperkins, narsis, rhn-bugs, smartin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-03-24 18:12:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
reassigned old narsis bugs to gdk. This bug has been closed due to inactivity. Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Description of problem: There is a need to provide customers, partners and internal Red Hat groups with the ability to get systems to specific configurations in time on the Enterprise Linux line of products. These specific points in time are referred to as Quarterly Updates. The intent is to release errata in bundles every quarter. The requirement is simple. A system should be able to be installed from ISOs, and when subscribed to the Quarterly Update channel, the system then receives all of the required updates to get that system to that specific Quarterly Update level. The Quarterly Update channels are voluntary. Customers can still subscribe to the base channel if desired. There are no requirements to manage systems between Quarterly Update child channel versions or rollback. Getting a system up to date (via base channel) from a Quarterly Update level should work. Version-Release number of selected component (if applicable): How reproducible: Didn't try Steps to Reproduce: 1.N/A 2. 3. Additional info: