[Package Known issue trace] Greenplum package only support py2 deployment scripts.

@pf-qiu 
This issue is for tracing the following greenplum packages across multiple openEuler LTS versions, such as openEuler 20.03 LTS SP2 -> openEuler 22.03 LTS . The protocol of openEuler s/w package should be keep all packages to be continuity. So Greenplum Chinese Community should consider how to make it support py3 in upstream or pushing upstream community to support py3 in the following releases.

Currently, from the TC meeting Archive [ARCHIVE](https://etherpad.openeuler.org/p/TC-DB-meetings-2021-7-7), gpdb 6.16.2 package was accepted by TC team and will locate into openEuler 20.03 LTS SP2 UPDATE. But current situation is that:
1. Master branch doesn't support py3 anymore, so openEuler CI won't pass. gpdb 6.16.2(py2 support only) can not be merged into master branch.
2. We create another branch which named 'openEuler-20.03-LTS-Next' from master branch directly, and make the new branch as the development branch for openEuler 20.03. This means the following PR for openEuler 20.03 will be merged into 'openEuler-20.03-LTS-Next' branch, not 'master'.
3. Once we finish the development on 'openEuler-20.03-LTS-Next' branch for openEuler 20.03 SP2, we will create the official branch for 20.03 LTS SP2, which is named as "openEuler-20.03-LTS-SP2". Then the gpdb 6.16.2 package will locate in openEuler 20.03 LTS SP2 UPDATE.

And another thing needs to be noticed here, for the following openEuler 22.03 LTS. The community package protocol is:
release system will fork the master branch into a new LTS development branch, such as "openEuler-22.03-LTS-Next". The next openEuler LTS version should develop on it. That means the master branch should support py3 before the release system fork the new LTS development branch for openEuler 22.03 LTS. For example, 20.03 LTS, release system forked a version from master on March in 2020(20.03 master), then create a LTS development branch 'openEuler-20.03-LTS-Next' for 20.03 LTS. Before the 20.03 release, it forked 'openEuler-20.03-LTS-SP1' branch from 'openEuler-20.03-LTS-Next' as official release branch(build/release package on it).

This raises a problem to Greenplum Chinese community. When we can merge gpdb version（support py3） into master branch?  You guys @pf-qiu needs to aware the time/deadline.

src-openEuler/gpdb

内容风险标识

评论 (1)

src-openEuler/gpdb .gitee-modal { width: 500px !important; }

内容风险标识