This is an automated email from the ASF dual-hosted git repository.
meonkeys pushed a commit to branch release/1.14.0
in repository https://gitbox.apache.org/repos/asf/fineract.git
The following commit(s) were added to refs/heads/release/1.14.0 by this push:
new 9977fb3fcb update manual release instructions
9977fb3fcb is described below
commit 9977fb3fcbaf647eeb41948c154530926fe2d351
Author: Adam Monsen <[email protected]>
AuthorDate: Mon Dec 22 12:40:03 2025 -0800
update manual release instructions
Not gonna lie, I'm getting tired of maintaining this second source of
truth. Hopefully my laziness, impatience, and hubris will tip the scales far
enough to delete it.
---
buildSrc/src/main/resources/instructions/step12.txt.ftl | 3 ++-
buildSrc/src/main/resources/instructions/step13.txt.ftl | 1 +
buildSrc/src/main/resources/instructions/step9.txt.ftl | 13 +------------
3 files changed, 4 insertions(+), 13 deletions(-)
diff --git a/buildSrc/src/main/resources/instructions/step12.txt.ftl
b/buildSrc/src/main/resources/instructions/step12.txt.ftl
index 22c8bec32d..59f418dfc5 100644
--- a/buildSrc/src/main/resources/instructions/step12.txt.ftl
+++ b/buildSrc/src/main/resources/instructions/step12.txt.ftl
@@ -24,6 +24,7 @@
Move the release candidate from the dev area to the release area using a
Subversion server-side copy:
-svn mv
https://dist.apache.org/repos/dist/dev/fineract/${project['fineract.release.version']}
https://dist.apache.org/repos/dist/release /fineract/
+# this is a remote operation
+svn mv -m "Release Fineract 1.14.0 🚢"
https://dist.apache.org/repos/dist/dev/fineract/${project['fineract.release.version']}
https://dist.apache.org/repos/dist/release/fineract/
[INSTRUCTIONS:END]
diff --git a/buildSrc/src/main/resources/instructions/step13.txt.ftl
b/buildSrc/src/main/resources/instructions/step13.txt.ftl
index 3a734bc711..db0b697126 100644
--- a/buildSrc/src/main/resources/instructions/step13.txt.ftl
+++ b/buildSrc/src/main/resources/instructions/step13.txt.ftl
@@ -30,5 +30,6 @@ and make sure that everything on the release tag is merged to
develop and that e
>> git push origin develop
>> git branch -D release/${project['fineract.release.version']}
>> git push origin :release/${project['fineract.release.version']}
+>> git describe
[INSTRUCTIONS:END]
diff --git a/buildSrc/src/main/resources/instructions/step9.txt.ftl
b/buildSrc/src/main/resources/instructions/step9.txt.ftl
index 5d2cae8d92..ee7b00a5f8 100644
--- a/buildSrc/src/main/resources/instructions/step9.txt.ftl
+++ b/buildSrc/src/main/resources/instructions/step9.txt.ftl
@@ -22,17 +22,6 @@
[INSTRUCTIONS:START]
-Following are the typical things we need to verify before voting on a release
candidate. And the release manager should verify them too before calling out a
vote.
-
-Make sure release artifacts are hosted at
https://dist.apache.org/repos/dist/dev/fineract
-
-* Release candidates should be in format
apache-fineract-bin-${project['fineract.release.version']}.tar.gz
-* Verify signatures and hashes. You may have to import the public key of the
release manager to verify the signatures. (gpg --import KEYS or gpg --recv-key
<key id>)
-* Git tag matches the released bits (diff -rf)
-* Can compile docs and code successfully from source
-* Verify DISCLAIMER, NOTICE and LICENSE (year etc)
-* All files have correct headers (Rat check should be clean - gradlew rat)
-* No jar files in the source artifacts
-* Integration tests should work
+See
https://fineract.apache.org/docs/current/#_step_9_verify_distribution_staging
[INSTRUCTIONS:END]
