You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2024/04/03 20:51:49 UTC
(causeway) 01/03: fixes the' 'page-causewayrelvX' variable for v2 branch
This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a commit to branch v3
in repository https://gitbox.apache.org/repos/asf/causeway.git
commit e80b38a3d070ebd616e33c2f8e050d94233e1d76
Author: danhaywood <da...@haywood-associates.co.uk>
AuthorDate: Wed Apr 3 21:48:03 2024 +0100
fixes the' 'page-causewayrelvX' variable for v2 branch
---
.../modules/ROOT/pages/post-release-successful.adoc | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
index a8ee77efcd..b25fa95542 100644
--- a/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
+++ b/antora/components/comguide/modules/ROOT/pages/post-release-successful.adoc
@@ -309,16 +309,16 @@ This has two benefits: first, the top-level `index.html` (in `supplemental-ui`)
[#create-doc-branch]
=== Create doc branch
-NOTE: At the time of writing we support two branches, `v2` and `v3`.
+NOTE: At the time of writing we support two branches, `master` (for v2) and `v3`.
Adjust these instructions if necessary.
First, we update all versions in `antora.yml`:
-* Update all `antora.yml` files to use the latest branch ({page-causewayrelv3}):
+* Update all `antora.yml` files to use the latest branch ({page-causewayrelv2}):
+
[source,bash,subs="attributes+"]
----
-find . -name antora.yml -exec sed -i 's/latest/{page-causewayrelv3}/g' {} \;
+find . -name antora.yml -exec sed -i 's/latest/{page-causewayrelv2}/g' {} \;
----
* Commit all these changes:
@@ -331,14 +331,14 @@ git commit -m "$CAUSEWAYJIRA: bumps antora.yml versions to $CAUSEWAYREL"
We now create a branch which can be referenced in the `site.yml`, later on.
-* We create the `{page-causewayrelv3}` branch.
+* We create the `{page-causewayrelv2}` branch.
+
-This mirrors the "rel/causeway-{page-causewayrelv3}" used for the formal (immutable) release tag, but is a branch because it allows us to move it, and must have this simplified name as it is used in the "edit page" link of the site template.
+This mirrors the "rel/causeway-{page-causewayrelv2}" used for the formal (immutable) release tag, but is a branch because it allows us to move it, and must have this simplified name as it is used in the "edit page" link of the site template.
+
[source,bash,subs="attributes+"]
----
-git branch {page-causewayrelv3}
-git push origin {page-causewayrelv3}
+git branch {page-causewayrelv2}
+git push origin {page-causewayrelv2}
----
Now we make sure that the docs in the new doc branch are actually up-to-date.
@@ -348,7 +348,7 @@ Now we make sure that the docs in the new doc branch are actually up-to-date.
+
[source,bash,subs="attributes+"]
----
-git checkout {page-causewayrelv3}
+git checkout {page-causewayrelv2}
----
* build framework