This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 460
Release Process
yungez edited this page Mar 5, 2018
·
1 revision
This page describes how to release a new version.
- A release branch is created: eg.
release/2.0.2. - Any critical issues should have fixed.
- Readme file updated to align with codes on behavior, version.
- CI passed.
- When there are no more additional critical issues, a release tag
2.0.2is created. - Code is built from
2.0.2tag. - Follow release automation to automatically publish packages to maven staging repository.
- Verify staged packages by testing release starters one by one.
- Promote to maven production repository after verification done.
- Keep this release branch.