Author: shuber
Date: Tue Mar 1 08:54:47 2022
New Revision: 1898504
URL: http://svn.apache.org/viewvc?rev=1898504&view=rev
Log:
[scm-publish] Updating Unomi website
Modified:
unomi/website/contribute/release-guide.html
unomi/website/documentation.html
Modified: unomi/website/contribute/release-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/release-guide.html?rev=1898504&r1=1898503&r2=1898504&view=diff
==============================================================================
--- unomi/website/contribute/release-guide.html (original)
+++ unomi/website/contribute/release-guide.html Tue Mar 1 08:54:47 2022
@@ -399,7 +399,7 @@ git tag -d unomi-root-2.0.0</code></pre>
<li>
Connect to <a
href="https://repository.apache.org/#stagingRepositories"
target="_blank">https://repository.apache.org/#stagingRepositories</a> and look
for the open staging repositories, you should have one. Select the staging
repositoriy and click on <code>release</code>.
</li>
- <li>Update the website to point to the new release on the
download page by first copying the current release to the archive page. Make
sure you change the links to use the archive.apache.org instead of the
closer.lua script (see other archived versions for example). Then you can
update the download page with the proper links to the new release (no direct
links to <code>www.apache.org/dist</code>, make sure you use the closer.lua
script). Be careful with links that contain & (ampersand) characters, they must
be replaced with & Finally on the home page update the news section to add
the release.
+ <li>Update the website (in project `unomi-site`) to point to the
new release on the download page by first copying the current release to the
archive page. Make sure you change the links to use the archive.apache.org
instead of the closer.lua script (see other archived versions for example).
Then you can update the download page with the proper links to the new release
(no direct links to <code>www.apache.org/dist</code>, make sure you use the
closer.lua script). Be careful with links that contain & (ampersand)
characters, they must be replaced with & Finally on the home page update
the news section to add the release.
<pre class="alert alert-primary"><code>git clone
https://gitbox.apache.org/repos/asf/unomi-site.git</code></pre>
Perform any modifications, notably change the versions in
the pom.xml file:
<pre class="alert alert-primary"><code> <properties>
@@ -413,27 +413,42 @@ git tag -d unomi-root-2.0.0</code></pre>
</li>
<li>
Test the site modifications using the generated site HTML
using Jekyll serve
- <pre class="alert alert-primary"><code>mvnw clean install
gem:exec@jekyll-serve-filtered</code></pre>
+ <pre class="alert alert-primary"><code>./mvnw clean
install gem:exec@jekyll-serve-filtered</code></pre>
Connect to http://127.0.0.1:4000 to check the
modifications. If you need to make more modifications,
simply relaunch the above line after modifying the HTML
files.
</li>
<li>
Deploy the web site changes using:
- <pre class="alert alert-primary"><code>mvnw clean install
-mvnw install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME
-Dpassword=YOUR_APACHE_PASSWORD</code></pre>
+ <pre class="alert alert-primary"><code>./mvnw clean install
+./mvnw install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME
-Dpassword=YOUR_APACHE_PASSWORD</code></pre>
</li>
<li>
Then make sure to commit all the changes to the web site's
git project:
- <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.0.0 Release website update"</code></pre>
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.0.0 Release website update"
+git push</code></pre>
</li>
</ol>
<h3 id="final-documentation">Documentation</h3>
<ol>
- <li>Check the generated site by opening
<code>target/staging/index.html</code> and check your changes and verify that
there are no broken links
+ <li>
+ In the `unomi` project, on the master, branch, make sure
that you have a archive for the current
+ branch in the `manual/src/archives` directory. If not,
create one with the current main version and
+ copy the contents of `manual/src/main` into the newly
created directory. Make sure you add all the
+ files to the git repository.
+ </li>
+ <li>
+ Modify the `generate-site.sh` and
`generate-site-and-upload.sh` if needed to add the new version
+ you added in the previous step.
+ </li>
+ <li>
+ Launch <pre class="alert
alert-primary"><code>./generate-site.sh</code></pre> from the project's
+ root directory.
+ </li>
+ <li>Check the generated site by opening
<code>target/staging/manual/index.html</code>
+ and check your changes and verify that there are no broken
links.
</li>
- <li>WAIT FOR THE MIRRORS TO SYNC (at least 24 hours)</li>
<li>
Upload the site modification by using:
<pre class="alert
alert-primary"><code>./generate-site-and-upload.sh APACHE_LDAP_USERNAME
APACHE_LDAP_PASSWORD</code></pre>
@@ -453,6 +468,10 @@ cd 2.0.0
svn add unomi-manual*
svn commit -m "Update Unomi manual packages"</code></pre>
</li>
+ <li>
+ Go back to the site project and make sure you update the
documentation page to link to the proper
+ versions of the documents.
+ </li>
</ol>
<h3 id="final-docker">Docker image</h3>
Modified: unomi/website/documentation.html
URL:
http://svn.apache.org/viewvc/unomi/website/documentation.html?rev=1898504&r1=1898503&r2=1898504&view=diff
==============================================================================
--- unomi/website/documentation.html (original)
+++ unomi/website/documentation.html Tue Mar 1 08:54:47 2022
@@ -89,16 +89,16 @@
<div class="card flex-md-row mb-4 box-shadow h-md-250">
<div class="card-body d-flex flex-column align-items-start">
<strong class="d-inline-block mb-2 text-success"><i class="fas
fa-circle"></i> Stable</strong>
- <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">1.5.7</span></h3>
- <div class="mb-1 text-muted">Last update: July 27th, 2021</div>
+ <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">1.6.0</span></h3>
+ <div class="mb-1 text-muted">Last update: February 28th,
2022</div>
<p class="card-text">
- <a href="manual/1_5_x/index.html">online</a><br>
- <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.zip">html
(zipped)</a>
- [ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.zip.asc">PGP</a>
|
- <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.zip.sha512">SHA512</a>
]<br>
- <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.pdf">pdf</a>
- [ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.pdf.asc">PGP</a>
|
- <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.5.4/unomi-manual-1_5_x.pdf.sha512">SHA512</a>
]
+ <a href="manual/1_6_x/index.html">online</a><br>
+ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.zip">html
(zipped)</a>
+ [ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.zip.asc">PGP</a>
|
+ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.zip.sha512">SHA512</a>
]<br>
+ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.pdf">pdf</a>
+ [ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.pdf.asc">PGP</a>
|
+ <a target="_blank"
href="https://dist.apache.org/repos/dist/release/unomi/1.6.0/unomi-manual-1_6_x.pdf.sha512">SHA512</a>
]
-->
</p>
</div>