This is an automated email from the ASF dual-hosted git repository.

meonkeys pushed a commit to branch release/1.16.0
in repository https://gitbox.apache.org/repos/asf/fineract.git


The following commit(s) were added to refs/heads/release/1.16.0 by this push:
     new bb0a4eae60 improve release instructions
bb0a4eae60 is described below

commit bb0a4eae60031394b96b262c3077e405c34154f9
Author: Adam Monsen <[email protected]>
AuthorDate: Tue Oct 20 09:26:19 2026 -0700

    improve release instructions
    
    - fix `git switch` in step 5 (we've already created the branch)
    - tidy up some grammar in step 3
    - improve step 13 merge justification
    - improve ATR instructions in steps 10 and 11
---
 fineract-doc/src/docs/en/chapters/release/process-step03.adoc | 8 ++++----
 fineract-doc/src/docs/en/chapters/release/process-step05.adoc | 2 +-
 fineract-doc/src/docs/en/chapters/release/process-step10.adoc | 2 --
 fineract-doc/src/docs/en/chapters/release/process-step11.adoc | 2 ++
 fineract-doc/src/docs/en/chapters/release/process-step13.adoc | 2 +-
 5 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/fineract-doc/src/docs/en/chapters/release/process-step03.adoc 
b/fineract-doc/src/docs/en/chapters/release/process-step03.adoc
index 92b179a8b6..ba0902e023 100644
--- a/fineract-doc/src/docs/en/chapters/release/process-step03.adoc
+++ b/fineract-doc/src/docs/en/chapters/release/process-step03.adoc
@@ -14,7 +14,7 @@ git clone [email protected]:apache/fineract.git
 cd fineract
 ----
 
-2. Check that current HEAD points to commit on which you want to base new  
release branch. Checkout a particular earlier commit if not.
+2. Confirm current HEAD points to desired commit
 +
 [source,bash]
 ----
@@ -22,14 +22,14 @@ git log <1>
 ----
 <1> Check current branch history. HEAD should point to commit that you want to 
be base for your release branch
 
-3. Create a new release branch using the version number
+3. Create new release branch
 +
 [source,bash,subs="attributes+,+macros"]
 ----
 git switch -c release/{revnumber}
 ----
 
-4. Push new branch to Apache Fineract repository
+4. Push new branch to shared public repository
 +
 [source,bash,subs="attributes+,+macros"]
 ----
@@ -38,7 +38,7 @@ git push origin release/{revnumber}
 
 5. Start new release notes page under 
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Releases[Fineract 
Releases]. The change list can be swiped from the JIRA release note tool (use 
the "text" format for the change log). See JIRA Cleanup above to ensure that 
the release notes generated by this tool are what you are expecting.
 
-6. Send en email announcing the new release branch on the earlier email thread
+6. Send email announcing the new release branch on the earlier email thread
 +
 [source,text]
 ----
diff --git a/fineract-doc/src/docs/en/chapters/release/process-step05.adoc 
b/fineract-doc/src/docs/en/chapters/release/process-step05.adoc
index 49a66d416d..82d478bcd7 100644
--- a/fineract-doc/src/docs/en/chapters/release/process-step05.adoc
+++ b/fineract-doc/src/docs/en/chapters/release/process-step05.adoc
@@ -6,7 +6,7 @@ Next, you create a git tag from the HEAD of the release's git 
branch.
 
 [source,bash,subs="attributes+,+macros"]
 ----
-git switch -c release/{revnumber} <1>
+git switch release/{revnumber} <1>
 git tag -a {revnumber} -m "Fineract {revnumber} release" -s
 git push origin tag {revnumber} <2>
 ----
diff --git a/fineract-doc/src/docs/en/chapters/release/process-step10.adoc 
b/fineract-doc/src/docs/en/chapters/release/process-step10.adoc
index e105bf12a4..c3c081ae25 100644
--- a/fineract-doc/src/docs/en/chapters/release/process-step10.adoc
+++ b/fineract-doc/src/docs/en/chapters/release/process-step10.adoc
@@ -4,8 +4,6 @@
 
 Initiate voting with https://release-test.apache.org[the ATR (ASF Trusted 
Releases) tool].
 
-Disable "Automatically publish to SVN when this vote resolves".
-
 == Gradle Task
 
 .Command
diff --git a/fineract-doc/src/docs/en/chapters/release/process-step11.adoc 
b/fineract-doc/src/docs/en/chapters/release/process-step11.adoc
index 81719e602f..9003fe2344 100644
--- a/fineract-doc/src/docs/en/chapters/release/process-step11.adoc
+++ b/fineract-doc/src/docs/en/chapters/release/process-step11.adoc
@@ -4,6 +4,8 @@
 
 Conclude voting with https://release-test.apache.org[the ATR (ASF Trusted 
Releases) tool].
 
+The ATR tally mechanism is not perfect. Manually confirm the tally and adjust 
as necessary before resolving the vote.
+
 == Gradle Task
 
 .Command
diff --git a/fineract-doc/src/docs/en/chapters/release/process-step13.adoc 
b/fineract-doc/src/docs/en/chapters/release/process-step13.adoc
index 2c3130c2f7..f0ef4dd350 100644
--- a/fineract-doc/src/docs/en/chapters/release/process-step13.adoc
+++ b/fineract-doc/src/docs/en/chapters/release/process-step13.adoc
@@ -13,7 +13,7 @@ git branch -D release/{revnumber}
 git push origin :release/{revnumber}
 git describe <2>
 ----
-<1> This merge is necessary for posterity: It's how we're able to preserve and 
trace lineage from releases to descendent commit.
+<1> This merge ensures all future commits and releases descend from the tagged 
commit used to build this release.
 <2> The output must refer to the most recent release. For example, if your 
working copy is checked out to the `develop` branch, the current commit is 
`0762a012e`, and the latest release tag (28 commits ago) was `1.12.1`, the 
output of `git describe` would be `1.12.1-28-g0762a012e`.
 
 == Gradle Task

Reply via email to