From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
> + Name of the channel as it will be presented to users
> (example: Red Hat Super-Advanced Blopserver Version Zig.x)
Red Hat Enterprise Linux ES 2.1 beta
> + The public version of the GPG key with which the packages are
> + A EULA, if different from the standard Red Hat public EULA.
Same EULA as that of As 2.1 x86 beta errata.
> + The package manifest, and where the signed packages will be found
> (ftp directory, porkchop directory, etc.)
(Note: both ES and WS beta channels are for instant ISOs only)
> + If a child channel, please give us the parent channel.
Separate parent channel.
> + If a private channel, please explain the users who should have
> (Example: give an "AS 2.1 3Q errata" subscription for every "AS 2.1"
Private beta testers (partners and customers) as selected by Product
Management. Donald Fischer <email@example.com> will maintain the list and
generate user logins for each beta tester.
> + If the channel will be paid or part of warranty service for another
> product, CRM *must* be involved (and we need to get CRM in the loop
> to determine their pieces of this process.)
This is a beta without support/warranty.
> + If the channel is a beta channel or a channel with a similarly
> limited lifetime, provide the anticipated expiration date of the
It is a beta channel. The official channel launch is scheduled for
March 3, 2003 at which time the beta will be retired. The final date
may shift but the beta channel should be removed only when we release
the official product.
> + If the channel is a base channel, provide a unique redhat-release
> tag so that we'll have a mechanism by which to assign a system to
> the new channel upon registration.
contents of /etc/redhat-release:
Red Hat Enterprise Linux ES release 2.0.92 (Panama)
> + A technical contact for testing.
Bill Goleman (firstname.lastname@example.org)
> + Expected release date AND time.
ASAP for beta (Mon 2/3 if possible)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** This bug has been marked as a duplicate of 83394 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.