Automated release process

[marsishandsome]

Automated release process

• release tikv client jar to maven central repo
• release notes to github
• add git tag

[iosmanthus]

Could we add a pre-release for the master branch? This will help a lot with regression testing.

[marsishandsome]

What do you mean by pre-release? How can it help with regression testing?

[zz-jason]

some thoughts about the release process:

• we need to ensure the JDK compatibility is not broken. It would be better to have tests for different JDK versions (Building for JDK9+ #154). Block the release unless the compatibility issues are fixed.
• we need to guarantee the TiKV compatibility is not broken. It would be better to have tests for different TiKV versions. Block the release unless the compatibility issues are fixed.

[marsishandsome]

some thoughts about the release process:

• we need to ensure the JDK compatibility is not broken. It would be better to have tests for different JDK versions (Building for JDK9+ #154). Block the release unless the compatibility issues are fixed.
• we need to guarantee the TiKV compatibility is not broken. It would be better to have tests for different TiKV versions. Block the release unless the compatibility issues are fixed.

better to create another two issues to track the tasks.

[iosmanthus]

What do you mean by pre-release? How can it help with regression testing?

pre-release means every time there is a commit pushed to the master branch, this event will trigger a build and upload the build tar to the maven repository. This release could be tested without rebuilding the whole repo in regression tests. It should be enough for QA to rebuild the test program to make a test.

[github-actions]

This issue is stale because it has been open 30 days with no activity.