43 lines
1.4 KiB
Markdown
43 lines
1.4 KiB
Markdown
|
# SIG Release
|
|||
|
|
English | [简体中文](./sig_release_cn.md)
|
|||
|
|
|
|||
|
|
Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md).
|
|||
|
|
|
|||
|
|
## SIG group work objectives and scope
|
|||
|
|
|
|||
|
|
### work goals
|
|||
|
|
1. Making OpenHarmony version release planning.
|
|||
|
|
2. Track the development status (updates or functional features) in the development/test cycle function.
|
|||
|
|
3. Release negotiation (within the scope of QA, release engineer, technology, etc.), participate in related groups and release related meetings.
|
|||
|
|
4. Responsible for the coordination of the project delivery process.
|
|||
|
|
|
|||
|
|
### work scope
|
|||
|
|
1. Community version release process.
|
|||
|
|
2. Community version release schedule.
|
|||
|
|
3. Community version release process and life cycle strategy description.
|
|||
|
|
|
|||
|
|
|
|||
|
|
### The repository
|
|||
|
|
- project name:
|
|||
|
|
-release-management: https://gitee.com/openharmony/release-management
|
|||
|
|
|
|||
|
|
## SIG Members
|
|||
|
|
|
|||
|
|
### Leader
|
|||
|
|
- [@fma66169](https://gitee.com/fma66169)
|
|||
|
|
|
|||
|
|
### Committers
|
|||
|
|
- @gitee account(https://gitee.com/xxx)
|
|||
|
|
|
|||
|
|
### Meetings
|
|||
|
|
- Meeting time：Biweekly Friday afternoon 16:30
|
|||
|
|
- Meeting application: [SIG_Release](https://shimo.im/sheets/KH3tTqXqctGWg3Vj/MODOC)
|
|||
|
|
- Meeting link: Welink
|
|||
|
|
- Meeting notification: [Subscribe to] (https://lists.openatom.io/postorius/lists/dev.openharmony.io) mailing list dev@openharmony.io for the meeting link
|
|||
|
|
|
|||
|
|
### Contact (optional)
|
|||
|
|
|
|||
|
|
- Mailing list：dev@openharmony.io
|
|||
|
|
- Slack group：xxx
|
|||
|
|
- Wechat group：HRS2030
|