This is an automated email from the ASF dual-hosted git repository.
xyz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar-client-go.git
The following commit(s) were added to refs/heads/master by this push:
new 6d9cbd8b Remove `VERSION` and `stable.txt` files (#1158)
6d9cbd8b is described below
commit 6d9cbd8ba3aa08b5285cceb0a4688dad57ae3171
Author: Zike Yang <[email protected]>
AuthorDate: Wed Mar 6 19:20:55 2024 +0800
Remove `VERSION` and `stable.txt` files (#1158)
### Motivation
We currently have two hardcoded version files in place: `VERSION` which
represents the current version and `stable.txt` which represents the current
stable version. However, I'm curious about the intended function of these
files. Are they merely for developers to conveniently reference the current and
stable versions? And what is our approach to managing these files? For
instance, how do we determine what constitutes a stable version? If there's no
compelling reason to keep these file [...]
Please see more discussion here:
https://lists.apache.org/thread/mrntb1y7ws173ohtdvz1v8q86pg50cn2
### Modifications
- Remove `VERSION` and `stable.txt` files.
---
VERSION | 3 ---
docs/release-process.md | 4 +---
stable.txt | 3 ---
3 files changed, 1 insertion(+), 9 deletions(-)
diff --git a/VERSION b/VERSION
deleted file mode 100644
index 725659e7..00000000
--- a/VERSION
+++ /dev/null
@@ -1,3 +0,0 @@
-// This version number refers to the currently released version number
-// Please fix the version when release.
-v0.12.0
diff --git a/docs/release-process.md b/docs/release-process.md
index 0832f17a..ab99ed67 100644
--- a/docs/release-process.md
+++ b/docs/release-process.md
@@ -35,9 +35,7 @@ cd pulsar-client-go
git checkout -b branch-0.X.0 origin/master
```
-2. Update the version and tag of a package.
-
-Update the information of the new release to the `VERSION` file and
`stable.txt` file and send a PR for requesting the changes.
+2. Create a tag for the release candidate.
During the release process, you can create a "candidate" tag which will get
promoted to the "real" final tag after verification and approval.
diff --git a/stable.txt b/stable.txt
deleted file mode 100644
index 8a5f2e8d..00000000
--- a/stable.txt
+++ /dev/null
@@ -1,3 +0,0 @@
-// This version number refers to the current stable version, generally is
`VERSION - 1`.
-// Please fix the version when release.
-v0.12.0
\ No newline at end of file