Requirements for Updating in Submission Pipeline

[zhoujing2022]

The current submission pipeline serves as a core process utilized by all module teams, including third-party teams, for releases. Therefore, its improvements and maintenance must be managed with increased transparency to ensure it does not impact production environment releases. For example:

• New improvement proposals should undergo evaluation and decision-making in architecture meetings or Product Owner (PO) meetings before being considered for inclusion in the change plan.
• Enhanced functionalities should undergo comprehensive testing, including collaboration with module teams, before being released.
• All user-related changes should be publicly disclosed through release notes or other forms of communication.
• All new changes must be documented in existing files, such as module-manifest.readme.
• Breaking changes should be avoided, or confirmation from all module teams must be obtained in advance to mitigate and prevent risks associated with breaking changes during release.

These measures aim to enhance transparency in the management of the submission pipeline, ensuring that any improvements or changes are thoroughly evaluated, tested, documented, and communicated to minimize the impact on the production environment.

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten