Actions
action #76138
closedask for scc enablement
Actions
Email sent to happy-customer:
Hello happy-customer team
Please add openSUSE 15.3 as a new product to SCC.
Please be aware that we're introducing s390x and armv7 is still undecided, but we'd like to intially track it.
Leap is officially Alpha since the beginning of Nov.
FYI: We'd like to demonstrate seamless migration from openSUSE Leap 15.3 to SLE 15 SP3 in the Public Beta (in February).
I would also like to ask you to deactivate openSUSE Leap 15.2.1 as it received no-go for release https://en.opensuse.org/Portal:Jump/Leap15.2.1:GoNogo
Successor of Leap 15.2 is therefore only Leap 15.3.
Request tracker for scc enablement of 15.3: https://progress.opensuse.org/issues/76138
OBS project: https://build.opensuse.org/project/show/openSUSE:Leap:15.3
He're the questionary
Release manager:
Lubos Kocman
Product name, CPE:
CPE_NAME="cpe://o:opensuse:leap:15.3"
Base products:
It is a base product
Extensions/Modules:
No
Architectures:
x86_64, s390x, ppc64le, aarch64, armv7
# Yes s390x as well, armv7 is still being questioned
Dependency: (for >= SLES15 modules and extensions)
No dependencies
Predecessor products:
openSUSE Leap 15.2
(If this is a module/extension) Enable automatically on migration?
If this is a module or an extension which wasn't available on SLE12, we
can enable it automatically when a system
migrates from SLE12 to SLE15. Should this be the case?
Needs subscription?:
No
Family:
sles (the only supported migration from Leap is to SLES)
Alpha test?:
No
Beta test?:
Yes (we're currently in sort of beta) so it would be useful to have it
as well
Release dates: When should the product be published by us?
FCS date: 7th July (tentative) https://en.opensuse.org/openSUSE:Roadmap
Under NDA?:
No
Go/No-go date:
Jun 30th is scheduled date for the GM build. We'd decide around this date.
Was blocked on poo#76111. This is now resolved