Project

General

Profile

action #56093 » New product enablement_ Leap 15.2.eml

lnussel, 2019-09-02 12:18

 
From: Ludwig Nussel <ludwig.nussel@suse.de>
Subject: New product enablement: Leap 15.2
To: SCC Team <happy-customer@suse.de>
Organization: SUSE Linux GmbH
Message-ID: <564dee72-8262-ed61-235c-4c1826021520@suse.de>
Date: Fri, 30 Aug 2019 15:00:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Thunderbird/60.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit

Hi,

This is a request for a new product to be enabled in SCC
### Required information

**Release manager**:
Ludwig Nussel <ludwig.nussel@suse.de> backups Max Lin <mlin@suse.de>, Luboš Kocman <lubos.kocman@suse.com>

**Product name, CPE:**
> Helps us to clearly identify product (needs to be listed on
https://api.suse.de/public/source/SUSE?view=productlist&expand=1&format=xml).

So far only on api.opensuse.org:

* <product name="openSUSE" cpe="cpe:/o:opensuse:opensuse:15.2" originproject="openSUSE:Leap:15.2"

TBD: will try to rename to opensuse:leap:15.2

**Base products:**
> (`cpe`s for ibs products) If the product is an extension or module, specify on which base products it can be installed.

n/a

**Extensions/Modules:**
> If the requested product is a base, which modules and extensions can be installed on it?

* <product name="openSUSE-Addon-NonOss" cpe="cpe:/o:opensuse:opensuse-addon-nonoss:15.2"
originproject="openSUSE:Leap:15.2">


**Archs:**
> Architectures to be enabled.

x86_64

**Dependencies:** (for >= SLES15 modules and extensions)
> If a module or extension - specify which module or extensions it depends on

n/a

**Predecessor products:**
> (`cpe`s for ibs products, `identifier` for NCC products) This defines the migration paths.
cpe:/o:opensuse:opensuse:15.1

**Free?:**
> Is the product free of charge? Modules for example.

Yes, all of it.

**(If non-free) Product class for each architecture:**
> This determines on which subscriptions the product will be available. We can help you with that if you
have an example registration code, SKU, or part number for that offering.

n/a

**Family:**
> This determines in which category the product will be shown on the SCC dashboard.
Choose one from: `["sles", "sle-webyast", "sled", "sle-slms", "sle-ha", "suse-manager", "suse-studio", "sle-rt", "sle-pos", "suse-cloud", "sle-ha-geo", "res", "suse-vmdp", "sle-sdk", "sle-smt", "sle-sap", "ses"]`

doesn't fit any really but sles is closest

**Alpha test?:**
> Should we export the product on the -ALPHA product class?
For existing products, you can find Alpha keys in the SCC Alpha Keys organization in SCC:
https://scc.suse.com/subscriptions?current_organization=309910.

no idea what that means :)

**Beta test?:**
> Should we export the product on the -BETA product class and generate beta keys?
> How many keys to generate and whom to send to?
> By default, the beta program ends on the date of the FCS.
> When should the product be published by us?

Rolling development model. Beta phase probably ends April. FCS expected May but no concrete date yet.


**Under NDA?:**
> Please be aware that if your product is under NDA, enabling it in the beta or FCS state in SCC
will expose it to the public, potentially breaking the NDA.

No NDA

**OEM only offering?:**
> Yes/No. HINT: If it doesn't appear on the Corporate Price List, but on the IHV Price List (or an internal price list specific to a particular IHV), it's OEM only")

No

**Go/NoGo**:
> If you have a final go/no-go meeting, and the date of release should be shifted - inform SCC team with definitive ACK.


cu
Ludwig

--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
    (1-1/1)