Feature: design for release

[cubxxw]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've discussed this feature request in the OpenIMSDK Slack and got positive feedback

Is this feature request related to a problem?

No

Problem Description

OpenIM needs to have a clear and automated process for release, and the CHANGELOG is automatically generated for each release.

Solution Description

Referring to the release and design ideas of some excellent projects, I summarize the following steps:

1. The CHANGELOG is automatically generated
2. Automatically generate the version number
3. Consistent behavior
4. The bot makes a PR for each week's contribution and summarizes it

Benefits

With professional, more automated engineering

Potential Drawbacks

No response

Additional Information

No response

[cubxxw]

https://github.com/git-chglog/git-chglog:
CHANGELOG generator implemented in Go (Golang).

[cubxxw]

https://github.com/arnaud-deprez/gsemver: gsemver uses git commit convention to automate the generation of your next semver version

[cubxxw]

We can write a script to control the version number of the entire project

version=v`gsemver bump`
if [ -z "`git tag -l $version`" ];then
  git tag -a -m "release version $version" $version
fi

[kubbot]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.