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

danhaywood pushed a commit to branch CAUSEWAY-3898
in repository https://gitbox.apache.org/repos/asf/causeway.git

commit 2257950b9ace04a89eed069e9a2b1f603f12fdf4
Author: Dan Haywood <[email protected]>
AuthorDate: Wed Oct 8 10:29:56 2025 +0100

    CAUSEWAY-3898: updates relesae procedure docs
---
 .../comguide/modules/ROOT/pages/cutting-a-release.adoc      | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git 
a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc 
b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
index 7b0049e6251..ce86b734542 100644
--- a/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/cutting-a-release.adoc
@@ -239,25 +239,14 @@ git push origin $CAUSEWAYBRANCH -u
 
 For 
link:https://maven.apache.org/guides/mini/guide-reproducible-builds.html[reproducibility],
 the `project.build.outputTimestamp` property must be updated to a hard-coded 
value.
 
-Locate this property in `bom/pom.xml` and update to the current date/time.
+Locate this property in `parent/pom.xml` and update to the current date/time.
 
 
-=== Switch to the `bom` directory
-
-The remainder of the release process is performed from the context of the 
`bom` directory:
-
-[source,bash,subs="attributes+"]
-----
-cd bom
-----
-
 === Bump projects to `$CAUSEWAYREL`
 
 We use `mvnd versions:set` to manually bump the release version.
 (After release, there is a 
xref:comguide:ROOT:cutting-a-release.adoc#reset-revision-property[similar step 
at the end] to reset back to a `-SNAPSHOT` version).
 
-(Still in the `bom` directory), the steps are:
-
 * First we bump the framework's `pom.xml` files:
 +
 [source,bash,subs="attributes+"]

Reply via email to