You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2018/01/09 06:23:18 UTC
[isis] 04/06: ISIS-1465: further updates to website publish process
This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/isis.git
commit 64e46097f91627032be234e7f01af6b354ec5732
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Mon Jan 8 21:27:39 2018 +0000
ISIS-1465: further updates to website publish process
---
adocs/documentation/pom.xml | 4 ++-
.../cgcom/_cgcom_post-release-successful.adoc | 32 ++++++++++++++++++----
2 files changed, 29 insertions(+), 7 deletions(-)
diff --git a/adocs/documentation/pom.xml b/adocs/documentation/pom.xml
index c693b15..ecfdcd1 100644
--- a/adocs/documentation/pom.xml
+++ b/adocs/documentation/pom.xml
@@ -29,7 +29,7 @@
<groupId>org.apache.isis.docs</groupId>
<artifactId>isis-documentation</artifactId>
- <version>1.15.0-SNAPSHOT</version>
+ <version>2.0.0-M1-SNAPSHOT</version>
<packaging>pom</packaging>
<name>Apache Isis Docs</name>
@@ -218,6 +218,8 @@
<echo message=""/>
<echo message="deleting everything in ${isis-site-latest.dir}"/>
<echo message=""/>
+ <mkdir
+ dir="${isis-site-latest.dir}"/>
<delete includeemptydirs="true">
<fileset dir="${isis-site-latest.dir}" includes="**/*"/>
</delete>
diff --git a/adocs/documentation/src/main/asciidoc/guides/cgcom/_cgcom_post-release-successful.adoc b/adocs/documentation/src/main/asciidoc/guides/cgcom/_cgcom_post-release-successful.adoc
index ffe6e87..9b10e64 100644
--- a/adocs/documentation/src/main/asciidoc/guides/cgcom/_cgcom_post-release-successful.adoc
+++ b/adocs/documentation/src/main/asciidoc/guides/cgcom/_cgcom_post-release-successful.adoc
@@ -281,12 +281,13 @@ For more information on DOAP files, see these http://projects.apache.org/doap.ht
This will have published to the `SNAPSHOT` directory of the `isis-site` repo.
Now, in the `isis-site` repo itself:
-* double check that a copy of current exists as a named directory under `content/versions`
+* double check that a copy of `current` exists as a named directory under `content/versions`
+
-If for any reason it isn't there, then create a copy.
+If for any reason it isn't there, then create a copy before it gets deleted in the step below.
+Also, take a copy of the `index.html` with one that redirects up to the home page (see a few steps below for an example).
-* delete the current version and rename `SNAPSHOT` as `current`:
+* delete the `current` version and then rename the just-published `SNAPSHOT` as `current`:
+
[source,bash]
@@ -295,7 +296,7 @@ rm -rf content/versions/current
mv content/versions/SNAPSHOT content/versions/current
----
-* take a copy of the new `current` version as a named version:
+* take a copy of the new `current` version as its appropriately named version:
+
For example:
@@ -305,11 +306,30 @@ For example:
cp -rf content/versions/current content/versions/2.0.0-M1
----
+* update the new named version's `index.html` with one that will redirect back to the home page.
+
++
+You can take a copy from one of the older named versions, or just use this text:
++
+[source,html]
+----
+<html>
+ <head>
+ <title>Redirecting to index.html</title>
+ <meta http-equiv="refresh" content="1; URL=../../index.html">
+ <meta name="keywords" content="automatic redirection">
+ </head>
+ <body>
+ Redirecting to <a href="../../index.html">index.html</a>...
+ </body>
+</html>
+----
+
* In the root `index.html`, update the menu to reference the new version.
-At this point the files in the root (directly under `content`) will still be out of date; the publish process simply takes a copy of whatever is in `content/versions/current`.
+At this point the files in the root (directly under `content`) will still be out of date; the publish process simply preserves whatever is in `content/versions/current`.
Also, the `SNAPSHOT` will be missing (above it was renamed to `current`).
-To fix this, simply publish the website one more time (from the `isis` main repo).
+To fix both of these issues, simply publish the website one more time (from the `isis` main repo).
Finally, preview the changes (in the `isis-site`).
If everything looks ok, then push the changes to make live.
--
To stop receiving notification emails like this one, please contact
"commits@isis.apache.org" <co...@isis.apache.org>.