各位openeuler社区的maintainer、committer和contributor好,
openEuler社区master分层构建&版本基线管控优化正式上线测试,欢迎开发者体验在release-management一个PR一步到位完成增加/移动/删除(删除请谨慎)! 操作指导:https://gitee.com/openeuler/release-management/blob/master/openEuler%E5%BC%8...
特别是openEuler-22.09,我们对原有的冗长的pckg-mgmt.yaml做了拆分: [cid:image002.jpg@01D8A10D.F7C29180]
From: xiasenlin Sent: Tuesday, July 26, 2022 9:09 AM To: 'dev@openeuler.org' dev@openeuler.org; 'tc@openeuler.org' tc@openeuler.org; 'release@openeuler.org' release@openeuler.org Cc: senlinyyds@outlook.com Subject: 【openEuler社区master分层构建&版本基线管控优化上线里程碑】
各位openeuler社区的maintainer、committer和contributor好,
openEuler社区master分层构建&版本基线管控优化即将上线,里程碑如下: 1. master分支纳入release-management管控&分层构建——7/27 2. openEuler-22.09基线管控优化——7/27 3. multi-version分支、Next开发分支纳入release-management管控——7/30
上线须知:
1. 开发者提交PR变更软件包指导:https://gitee.com/openeuler/release-management/blob/master/openEuler%E5%BC%8...
2. 社区对master分支工程做的分层project,如无特别需求,由CICD sig组主导软件包分层,开发者如往常提交PR至openEuler:Mainlien/openEuler:Epol即可。若开发者对于具体软件包的分层有新的建议,欢迎提交issue或者邮件交流!
3.2022/7/27之后,master及openEuler-22.09版本分支对应project的软件包变更入口,统一收归到release-management,即开发者不必再前往obs_meta提交PR!
4.2022/7/27~2022/7/30,下列分支对应project的软件包变更遵循原有流程:https://gitee.com/openeuler/release-management/issues/I4U2VN?from=project-is... openEuler-20.03-LTS-SP1 openEuler-20.03-LTS-SP3 openEuler-22.03-LTS openEuler-22.03-LTS-Next
5.2022/730之后,除已停维版本分支,所有开发及版本分支对应project的软件包变更入口,统一收归到release-management,即开发者不必再前往obs_meta提交PR!
6.已停维版本分支原则上不再接受软件包变更PR:openEuler-20.03-LTShttps://gitee.com/openeuler/release-management/tree/master/openEuler-20.03-LTS/ openEuler-20.03-LTShttps://gitee.com/openeuler/release-management/tree/master/openEuler-20.03-LTS-Next/openEuler-20.03-LTS-SP2https://gitee.com/openeuler/release-management/tree/master/openEuler-20.03-LTS-SP2/openEuler-20.09https://gitee.com/openeuler/release-management/tree/master/openEuler-20.09/openEuler-21.03https://gitee.com/openeuler/release-management/tree/master/openEuler-21.03/openEuler-21.09https://gitee.com/openeuler/release-management/tree/master/openEuler-21.09/
以上,如果各位有更好的意见和想法,欢迎在CICD sig提交issue或者邮件交流!