From d6560c0cdf8571ee835cfa470e250cacac98617a Mon Sep 17 00:00:00 2001
From: EthanForAi <128460220+EthanForAi@users.noreply.github.com>
Date: Thu, 27 Jul 2023 16:26:29 +0800
Subject: [PATCH] feat: add pre-release process

---
 docs/conversions/version.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/conversions/version.md b/docs/conversions/version.md
index a421dd549..4644255c6 100644
--- a/docs/conversions/version.md
+++ b/docs/conversions/version.md
@@ -53,5 +53,9 @@ git merge release-v3.1
 # Push the updates to the main branch
 git push origin main
 ```
-
-Remember, communication with your team is key throughout this process, keeping everyone up-to-date with the changes being made.
\ No newline at end of file
+##  Pre-release Process
+The pre-release process of OpenIM, including the three repositories Open-IM-Server/chat/open-im-sdk-core, is as follows:
+(1) Check out a new branch named 'develop' from the 'main' branch;
+(2) Generate the SDK on the 'develop' branch of open-im-sdk-core, and deploy the 'develop' branch in chat/Open-IM-Server;
+(3) Test by packaging the apk with the new version of SDK;
+(4) The bug-fixing process on the 'develop' branch: Fork from the 'develop' branch to the personal repository, then create a pull request to merge into the 'develop' branch, and finally merge into the 'main' branch.