This is an automated email from the ASF dual-hosted git repository. meonkeys pushed a commit to branch release-doc-fixes in repository https://gitbox.apache.org/repos/asf/fineract.git
commit 4112ade7e0958faebf9311dc61dea8ecd118f706 Author: Adam Monsen <[email protected]> AuthorDate: Tue Jul 15 09:18:37 2025 -0700 WIP --- fineract-doc/src/docs/en/chapters/release/process-step03.adoc | 2 ++ fineract-doc/src/docs/en/chapters/release/process-step06.adoc | 2 ++ 2 files changed, 4 insertions(+) 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 8d43fb0d83..c0b19ffb66 100644 --- a/fineract-doc/src/docs/en/chapters/release/process-step03.adoc +++ b/fineract-doc/src/docs/en/chapters/release/process-step03.adoc @@ -6,6 +6,8 @@ Communicate with the community. You do not need to start a new email thread on t You do not need to ask committers to hold off any commits until you have branched finished, as it's always possible to fast-forward the branch to latest develop, or cherry-pick last minute changes to it. People should be able to continue working on the develop branch on bug fixes and great new features for the next release while the release process for the current release is being worked through. +// FIXME - don't use {revnumber}, and/or make sure `-SNAPSHOT` is left out + 1. Clone fresh repository copy + [source,bash] diff --git a/fineract-doc/src/docs/en/chapters/release/process-step06.adoc b/fineract-doc/src/docs/en/chapters/release/process-step06.adoc index 28c160d531..bf837a02e9 100644 --- a/fineract-doc/src/docs/en/chapters/release/process-step06.adoc +++ b/fineract-doc/src/docs/en/chapters/release/process-step06.adoc @@ -4,6 +4,8 @@ Create source and binary tarballs. +// FIXME - clean this up? focus on what commands should actually be run + [source,bash,subs="attributes+"] ---- % ./gradlew --rerun-tasks srcDistTar binaryDistTar <1>
