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
commit 0f6f182193b19578844f837418f9330f5c00e7f6 Author: Adam Monsen <[email protected]> AuthorDate: Thu Dec 18 09:15:11 2025 -0800 improve start release notes wording in step 3 --- fineract-doc/src/docs/en/chapters/release/process-step03.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 48e39e5e93..1db633dd92 100644 --- a/fineract-doc/src/docs/en/chapters/release/process-step03.adoc +++ b/fineract-doc/src/docs/en/chapters/release/process-step03.adoc @@ -36,7 +36,7 @@ git checkout -b release/{revnumber} git push origin release/{revnumber} ---- -5. Add new release notes in Release Folders. 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. +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 +
