Bug 141536 - contact for beta tests and sponsoring requests
Summary: contact for beta tests and sponsoring requests
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: redhat-release
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: dff
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-01 20:53 UTC by Florian Effenberger
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:12:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Florian Effenberger 2004-12-01 20:53:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5)
Gecko/20041108 Firefox/1.0

Description of problem:
Sorry for doing that via Bugzilla, but the @redhat.com website
contacts did not reply.

What is the right contact within Red Hat

   1. for applying for a (nonpublic) beta test?
   2. for asking for sponsorings of Red Hat products?

Thanks!
Florian

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
N/A

Additional info:

Comment 2 Suzanne Hillman 2004-12-08 23:02:03 UTC
Internal RFE bug #142325 entered; will be considered for future releases.

Comment 3 Suzanne Hillman 2004-12-08 23:04:54 UTC
Meh. Wrong bug. Ignore comment #2. *sigh*

Comment 4 RHEL Program Management 2007-10-19 19:12:29 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


Note You need to log in before you can comment on or make changes to this bug.