是的
建议后面用
alpha, beta, rc 这样大家习惯的方案。
Alpha -> 集成，基本没有测试
Beta -> 基本功能可用
Rc -> 发布候选，通过测试，基本稳定
From: Zhoukang (A) [mailto:zhoukang7@huawei.com]
Sent: Monday, November 23, 2020 4:29 PM
To: Hufeng (Solar, Euler) <solar.hu@huawei.com>
Cc: dev@openeuler.org; tc <tc@openeuler.org>
Subject: [Dev] 答复: openEuler 20.03 LTS SP1转测试通知
社区不是应该有RC1, RC2等公测版本吗?
发件人: Hufeng (Solar, Euler)
[mailto:solar.hu@huawei.com]
发送时间: 2020年11月23日
16:20
收件人:
release@openeuler.org; dev@openeuler.org; tc <tc@openeuler.org>;
qa@openeuler.org;
Infra@openeuler.org
主题: [Tc] openEuler 20.03 LTS SP1转测试通知
目前通过和大家核对，以下特性除HA延期交付外，其他特性均完成合入。版本进入第一轮正式转测试。
测试期间发现的问题，请一并提issue，里程碑选择openEuler-20.03-LTS-SP1。方便问题过滤。
请相关责任人更新特性进展为Testing。
HA经过和sig组责任人沟通，当前暂不合入SP1版本。相关sig组同步进行测试，12月10日评审测试报告（包含两轮测试结论），评审通过后合入20.03
LTS SP1 EPOL工程。进行最后一轮回归。
版本取用路径如下：
http://117.78.1.88:82/dailybuilds/openeuler/openEuler-20.03-LTS-SP1/openeuler_2020-11-23-01-42-47/
该版本为测试周期内版本，仅用于测试，严禁商用，除版本测试必须的人员外，请勿扩散。
扩散和商用导致的后果openEuler社区不承担任何责任。
Release计划路径
https://gitee.com/openeuler/release-management/blob/master/openEuler-20.03-LTS-SP1/release-plan.md
|
Stange name |
Begin time |
End time |
|
Develop |
2020-10-12 |
2020-11-7 |
|
Comptibility |
2020-11-8 |
2020-11-18 |
|
Buil |
2020-11-19 |
2020-11-21 |
|
Test round 1（we are here） |
2020-11-23 |
2020-11-28 |
|
Test round 2 |
2020-11-30 |
2020-12-5 |
|
Test round 3 |
2020-12-7 |
2020-12-12 |
|
Test round 4 |
2020-12-14 |
2020-12-19 |
|
release |
2020-12-21 |
2020-12-22 |
|
no |
fetur |
status |
sig |
owner |
|
1 |
developing |
sig-HA |
yangzhao_kl |
|
|
2 |
developing |
|||
|
3 |
developing |
|||
|
4 |
developing |
|||
|
5 |
developing |
sig-python-modules |
||
|
6 |
developing |
DB |
||
|
7 |
developing |
sig-release-management |
||
|
8 |
developing |
sig-DDE |
||
|
9 |
developing |
|||
|
10 |
developing |
Desktop |
||
|
11 |
developing |
|||
|
12 |
developing |
Virt |
||
|
13 |
developing |
Virt |
||
|
14 |
developing |
Virt |
||
|
15 |
developing |
Virt |
||
|
16 |
developing |
|||
|
17 |
developing |
|||
|
18 |
developing |
|||
|
19 |
developing |
|||
|
20 |
developing |
Base-service |
||
|
21 |
developing |
Application |
||
|
22 |
developing |
Base-service |
||
|
23 |
developing |
|||
|
24 |
developing |
RaspberryPi |
||
|
25 |
developing |
sig_UKUI |
||
|
26 |
developing |
sig-OS-Builder |
||
|
27 |
developing |
|||
|
28 |
developing |
|||
|
29 |
developing |
|||
|
30 |
developing |
已知问题
|
序号 |
描述 |
关联软件 |
进展/结论 |
|
1 |
package abrt-atomic-2.13.0-9.oe1.aarch64 conflicts with abrt-addon-ccpp provided by abrt-addon-ccpp-2.13.0-9.oe1.aarch64 |
abrt |
已确认：abrt主包spec中对abrt-atomic下加了Conflicts，会与abrt-addon-ccpp冲突 |
|
2 |
package blktrace-1.2.0-14.oe1.aarch64 obsoletes iowatcher < 1.2.0-14.oe1 provided by iowatcher-1.0-7.oe1.aarch64 |
iowatcher |
已确认：blktrace已提供iowatcher，移除 |
|
3 |
package rdma-core-28.1-3.oe1.aarch64 obsoletes infiniband-diags provided by infiniband-diags-2.1.0-2.oe1.aarch64； |
infiniband |
已确认：在rdma-core升级到27.1版本时，已经提供了infiniband-diags的功能，移除 |
|
4 |
package fio-3.7-6.oe1.aarch64 requires libibverbs.so.1()(64bit), but none of the providers can be installed； |
infiniband |
已确认：因为缺少rdma-core提供的库文件，库文件没有，是因为rdma-core跟infiniband-diags冲突没安装上，修改方案同问题3 |
|
5 |
package libkcapi-devel-1.2.0-3.oe1.aarch64 obsoletes libkcapi-tests provided by libkcapi-tests-1.2.0-3.oe1.aarch64 |
libkcapi-devel |
已确认：删除多余的provides |
|
6 |
package mysql5-5.7.21-2.oe1.aarch64 conflicts with mariadb provided by mariadb-3:10.3.9-9.oe1.aarch64 |
mysql5 |
已确认：mysql与mariadb不能同时安装 |
|
7 |
package mvapich2-devel-2.3-8.oe1.aarch64 requires rdma-core-devel, but none of the providers can be installed |
infiniband |
已确认：因为缺少rdma-core提供的库文件，库文件没有，是因为rdma-core跟infiniband-diags冲突没安装上，修改方案同问题3 |
|
8 |
package pulseaudio-gdm-hooks-13.0-2.oe1.aarch64 requires gdm >= 1:2.22.0, but none of the providers can be installed |
pulseaudio |
已确认：gdm包已提供pulseaudio-gdm-hooks这个功能，移除 |
|
9 |
package python3-abrt-container-addon-2.13.0-9.oe1.aarch64 conflicts with python3-abrt-addon provided by python3-abrt-addon-2.13.0-9.oe1.noarch |
abrt |
已确认：abrt主包spec中对abrt-atomic下加了Conflicts，会与abrt-addon-ccpp冲突 |
|
10 |
package python3-pycryptodome-3.9.7-3.oe1.aarch64 conflicts with python3-crypto <= 2.6.1 provided by python3-crypto-2.6.1-26.oe1.aarch64 |
python-crypto |
已确认：python-crypto衰退软件，python-pycryptodome是python-crypto它的替代软件 |
|
11 |
Pxe安装后无法启动，问题正在确认 |
Selinux |
|