kubeedge
/
community
mirror of https://github.com/kubeedge/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add charter of release sig 

Signed-off-by: zhiying <zhiying.fang@daocloud.io>
This commit is contained in:
zhiying 2023-09-22 16:25:50 +08:00
parent aea94c60aa
commit 9010537fc1
2 changed files with 97 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
sig-release/README.md Normal file
View File

@ -0,0 +1,35 @@
# SIG Release
Ensure quality KubeEdge releases
The [charter](charter.md) defines the scope and governance of the Release Special Interest Group.
## Meetings
* Regular SIG Meeting: [Monday at 11:00-12:00 UTC+8](https://zoom.us/j/4167237304) (biweekly, starts on Oct. 30th 2023). [Convert to your timezone](https://www.thetimezoneconverter.com/?t=10%3A00%20am&tz=GMT%2B8&).
* [Meeting notes and Agenda](https://docs.google.com/document/d/1DCEr2fgFOWT3nXFopMBrWHoxMyd2JeuZ7FMGcrzEFlo/edit).
## Contact
- Slack: [#sig-release slack channel](https://kubeedge.slack.com)
- [Open Community Issues](https://github.com/kubeedge/kubeedge/issues)
- [Mailing list](https://groups.google.com/forum/#!forum/kubeedge)
## Leadership
### Chairs
The Chairs of the SIG run operations and processes governing the SIG.
- Shelley Bao (@Shelley-BaoYue), Huawei
- Zhiying Fang (@zhiyingfang2022), DaoCloud
### Technical Leads
The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.
- Shelley Bao (@Shelley-BaoYue), Huawei
- Zhiying Fang (@zhiyingfang2022), DaoCloud

62
sig-release/charter.md Normal file
View File

@ -0,0 +1,62 @@
# SIG Release Charter
This charter adheres to the conventions described in [KubeEdge Open Governance](https://github.com/kubeedge/community/blob/master/GOVERNANCE.md) and uses the Roles and Organization Management outlined in the governance doc.
## Scope
- Responsible for planning, coordinating, and managing software releases.
- Handling version numbers and tags to ensure consistency and traceability of versions.
- Maintain change logs to record new features, improvements, and issue fixes for each release.
- Writing and maintaining documentation related to versions, including release notes, installation guides, etc.
- Communicating version updates, significant changes, and release plans to users and the community.
- Automating the process of releasing software versions to improve efficiency and consistency.
### In scope
**Version Number Management:**
- Define version number allocation strategy, such as Semantic Versioning.
- Maintain version number allocation rules, including rules for incrementing major, minor, and patch versions.
- Handle management of pre-release versions and version previews, including alpha, beta, RC versions, etc.
**Release Planning and Timetable:**
- Develop the project's release plan and determine the timetable for version releases.
- Coordinate release timings to ensure consistency with other key events or dependencies.
**Release Candidate Management:**
- Ensure the build, testing, and validation processes for each release version.
- Responsible for creating and maintaining release candidates.
- Ensure documentation readiness for release candidates.
**Documentation Writing and Maintenance:**
- Create release notes documentation detailing new features, improvements, and bug fixes.
- Maintain version update logs documenting changes for each version.
- Update project documentation to reflect the features and requirements of new versions.
**Collaboration with Other SIGs and Project Teams:**
- Collaborate with development and testing teams to ensure the quality and reliability of versions.
- Interact with the community and users to address version-related issues and feedback.
- Work with the security team to ensure the security of release versions.
### Out of scope
- Development of specific functional features.
- Bug tracking and issue resolution.
- User support.
- Other tasks unrelated to version management and releases.
## Roles and Organization Management
This SIG follows and adheres to the Roles and Organization Management outlined in KubeEdge Open Governance and opts-in to updates and modifications to KubeEdge Open Governance.
### Additional responsibilities of Chairs
- Manage and curate the project boards associated with all sub-projects ahead of every SIG meeting so they may be discussed.
- Ensure the agenda is populated 24 hours in advance of the meeting, or the meeting is then cancelled.
- Report the SIG status at events and community meetings wherever possible.
- Actively promote diversity and inclusion in the SIG.
- Uphold the KubeEdge Code of Conduct especially in terms of personal behavior and responsibility.