CBSNexora/cbsnexora-backend
4
0
Fork 0
Code Issues Pull Requests Actions 37 Packages Projects Releases Wiki Activity

update manual release instructions

Browse Source 
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.
This commit is contained in:
Adam Monsen
2025-12-22 12:46:52 -08:00
parent e1b0329748
commit 9977fb3fcb
3 changed files with 4 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
buildSrc/src/main/resources/instructions/step12.txt.ftl
+2 -1
View File
@@ -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]
buildSrc/src/main/resources/instructions/step13.txt.ftl
+1
View File
@@ -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]
buildSrc/src/main/resources/instructions/step9.txt.ftl
+1 -12
View File
@@ -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]