Bug 586504
Summary: | RFE: Add Slide to Developer Installation Option | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | dt |
Component: | distribution | Assignee: | RHEL Program Management <pm-rhel> |
Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | borgan, jofernan, rvokal, salmy |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-09-07 03:20:31 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: |
Description
dt
2010-04-27 18:32:49 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. This feature request did not get resolved in time for Feature Freeze for the current Red Hat Enterprise Linux release and has now been denied. You may re-open your request by requesting your support representative to propose it for the next release. NOTE: Bugzilla is not a support tool The Bugzilla interface at bugzilla.redhat.com is used internally by Red Hat to process changes e.g. to Red Hat Enterprise Linux and related products, as well as by the Fedora Community to develop the Fedora Project. It is publicly available and everyone with an email address is able to create an account, file bugs, comment on bugs she or he has access to. Not all bugs are public though and not all issues filed are handled in the same way: it makes a huge difference who is behind a bug. Red Hat does monitor Bugzilla entries, and it does review them for inclusion in errata, etc. Nevertheless, as noted on the login page, Bugzilla is not a Support tool. It is an Engineering tool. It is used by Red Hat Engineering to track issues and product changes, as well as to interact with Egineering partners and other parties external to Red Hat on a technical level. So while all changes to Red Hat Enterprise Linux will at a point go through Bugzilla, this difference has a number of important consequences for general product issues filed directly through Bugzilla by external users without any privileged Engineering relationship: * Red Hat does NOT guarantee any response time or Service Level Agreement (SLA) for Bugzilla entries. - A review might happen immediately or after a time span of any length. The SLAs for Red Hat Enterprise Linux provided by Red Hat Support can be found at: https://www.redhat.com/support/policy/sla/production/ * Not all comments are publicly visible. - Red Hat Support provides customers with appropriate information excerpts and status updates from that. Red Hat does not commit to provide detailed explanations, or guidance in the context of Bugzilla. Therefore for example, Bugzilla entries might be closed as it seems without any further explanation, while Red Hat Support actually provides such explanation to customers filing through the regular support channels. * Issues coming through the regular support process, will always be prioritized higher than issues of similar impact and severity that are being filed directly through Bugzilla (unless the later get linked to customer support tickets). This means that they are more likely to be addressed and they are more likely to meet inclusion criteria consistent with the Red Hat Enterprise Linux life cycle policy: http://www.redhat.com/security/updates/errata/ * Work-arounds and Hotfixes if possible and appropriate are provided by Red Hat Support and through the regular support process. - This means that even before a permanent fix is made available through RHN, customers who raised a high severity issue through Red Hat Support, are likely to receive an interim solution. Red Hat provides common Bugzilla access in order provide efficient development community interaction and as much transparency as possible to our customers. Our Engineers are encouraged to provide non-customer specific and non-confidential information publicly as often as possible. So while Red Hat considers issues directly entered into Bugzilla valuable feedback - may it be as comments to existing Bugzilla entries or by opening a new one; for customers encountering production issues, Bugzilla is not the right channel. Therefore we ask our customers to file requests important for their production systems via our Support service. Only for those issues, we can ensure a consistent communication. Information about our production support process can be found at: http://www.redhat.com/support/process/ Bugzilla can always be used as a supportive channel to that communication. Note: If your customer is participating in the Academic program and has chosen to run a Subscription without support, they consequently have no access to Red Hat Support and thus no SLA. If you feel that this is insufficient for your use case, you should consider contacting the Red Hat Education specialist as described at: http://www.redhat.com/solutions/education/academic/individual/ This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. It has been proposed for the next release. If you would like it considered as an exception in the current release, please ask your support representative. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. Red Hat Enterprise Linux 6 has reached the end of Production 1 Phase of its Life Cycle (see https://access.redhat.com/support/policy/updates/errata/ for details). Accordingly, there are no plans to incorporate this feature in a future Red Hat Enterprise Linux 6 release. To request the feature be included in Red Hat Enterprise Linux 7, please re-open the request for Red Hat Enterprise 7 and provide additional business and/or technical information about the importance of this feature to you. |