This is an automated email from the ASF dual-hosted git repository.
dgriffon pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/unomi-site.git
The following commit(s) were added to refs/heads/master by this push:
new c613c56 UNOMI-801 : fix placeholders (#31)
c613c56 is described below
commit c613c568a0760a1eac4a629b037c4b25a1e2ea6e
Author: David Griffon <dgrif...@jahia.com>
AuthorDate: Tue Aug 29 17:38:03 2023 +0200
UNOMI-801 : fix placeholders (#31)
---
src/main/webapp/_data/unomi.yml | 2 +-
src/main/webapp/connectors.html | 2 +-
.../webapp/contribute/manual-release-guide.html | 122 ++++++++++-----------
src/main/webapp/contribute/release-guide.html | 60 +++++-----
src/main/webapp/documentation.html | 2 +-
5 files changed, 94 insertions(+), 94 deletions(-)
diff --git a/src/main/webapp/_data/unomi.yml b/src/main/webapp/_data/unomi.yml
index acd9f69..893848b 100644
--- a/src/main/webapp/_data/unomi.yml
+++ b/src/main/webapp/_data/unomi.yml
@@ -1,7 +1,7 @@
latest:
stable:
version: 2.3.0
- .development:
+ development:
version: 2.4.0-SNAPSHOT
next:
stable:
diff --git a/src/main/webapp/connectors.html b/src/main/webapp/connectors.html
index bfa2580..44ece48 100644
--- a/src/main/webapp/connectors.html
+++ b/src/main/webapp/connectors.html
@@ -25,7 +25,7 @@ layout: default
<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-warning"><i class="fas
fa-circle"></i> Unstable</strong>
- <h3 class="mb-0 text-dark">MailChimp <span
class="text-muted">${latest.development.version}</span></h3>
+ <h3 class="mb-0 text-dark">MailChimp <span class="text-muted">{{
site.data.unomi.latest.development.version }}</span></h3>
<div class="mb-1 text-muted">In development</div>
<p class="card-text">
<a href="manual/latest/index.html">Download</a><br>
diff --git a/src/main/webapp/contribute/manual-release-guide.html
b/src/main/webapp/contribute/manual-release-guide.html
index 8568d43..e7b58bd 100644
--- a/src/main/webapp/contribute/manual-release-guide.html
+++ b/src/main/webapp/contribute/manual-release-guide.html
@@ -137,12 +137,12 @@ gpg --verify test.txt.asc test.txt
<li>
Update all JIRAs, close the ones that are still not closed,
review tickets that can be closed, postpone to another release tickets that are
not managed now.
You can use this JIRA page: <a
href="https://issues.apache.org/jira/projects/UNOMI?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased";>Unomi
JIRA releases</a>.
- Then review the list of tickets that need to be updated,
also additionally you can check the list of commits since previous release and
insure they are closed using fix version: ${next.stable.version}.
- Ideally all tickets listed for version:
${next.stable.version} should be closed or moved to the next version in case
they are not finished/started.
+ Then review the list of tickets that need to be updated,
also additionally you can check the list of commits since previous release and
insure they are closed using fix version: {{
site.data.unomi.next.stable.version }}.
+ Ideally all tickets listed for version: {{
site.data.unomi.next.stable.version }} should be closed or moved to the next
version in case they are not finished/started.
</li>
<li>
Then you can also generate a release notes automatically
using: <a
href="https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12319220&version=12350150";>JIRA
release note</a>,
- By choosing the version: ${next.stable.version}. It will
be useful for linking the release notes in the voting mail.
+ By choosing the version: {{
site.data.unomi.next.stable.version }}. It will be useful for linking the
release notes in the voting mail.
</li>
</ol>
@@ -155,12 +155,12 @@ gpg --verify test.txt.asc test.txt
<li>
Simply checkout an existing branch for release
<pre class="alert alert-primary"><code>cd unomi
-git checkout unomi-${branch.version}
+git checkout unomi-{{ site.data.unomi.branch.version }}
</code></pre>
</li>
<li>OR Create a new branch if needed for the release using:
<pre class="alert alert-primary"><code>cd unomi
-git checkout -b unomi-${branch.version}
+git checkout -b unomi-{{ site.data.unomi.branch.version }}
</code></pre>
</li>
</ol>
@@ -177,7 +177,7 @@ git checkout -b unomi-${branch.version}
<pre class="alert alert-primary"><code>mvn clean install
-DskipITs=true -DskipTests=true -P
integration-tests,rat,apache-release,docker,\!run-tests</code></pre>
</li>
<li>Check that there are no JARs or ZIP files in the source
code, you can do this by looking at the generated RAT report here :
- <pre class="alert alert-primary"><code>less
target/unomi-root-${next.development.version}.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-{{ site.data.unomi.next.development.version
}}.rat</code></pre>
</li>
<li>Check that the KEYS file only contains signatures with
@apache.org addresses (if there are non @apache.org don’t remove them because
they have
been used to sign older releases)
@@ -203,11 +203,11 @@ gpg: signing failed: Inappropriate ioctl for
device</code></pre>
</li>
<li>Check into the target directory and unzip the source release
and compile it using:
<pre class="alert alert-primary"><code>pushd target
-gpg --verify unomi-root-${next.development.version}-source-release.zip.asc
unomi-root-${next.development.version}-source-release.zip
-shasum -a 512 unomi-root-${next.development.version}-source-release.zip
-cat unomi-root-${next.development.version}-source-release.zip.sha512
-unzip unomi-root-${next.development.version}-source-release.zip
-cd unomi-root-${next.development.version}
+gpg --verify unomi-root-{{ site.data.unomi.next.development.version
}}-source-release.zip.asc unomi-root-{{
site.data.unomi.next.development.version }}-source-release.zip
+shasum -a 512 unomi-root-{{ site.data.unomi.next.development.version
}}-source-release.zip
+cat unomi-root-{{ site.data.unomi.next.development.version
}}-source-release.zip.sha512
+unzip unomi-root-{{ site.data.unomi.next.development.version
}}-source-release.zip
+cd unomi-root-{{ site.data.unomi.next.development.version }}
mvn clean install
popd</code></pre>
to check that the packaged source build properly
@@ -230,12 +230,12 @@ popd</code></pre>
<li>If something fails, make sure you first drop the staging
repository created here: <a
href="https://repository.apache.org/#stagingRepositories";
target="_blank">https://repository.apache.org/#stagingRepositories</a>.<br>
If you need to relaunch the <code>release:perform</code> and don’t have a
release.properties, create a <code>release.properties</code> file with the
following contents:
<pre class="alert
alert-primary"><code>scm.url=scm:git:https://gitbox.apache.org/repos/asf?p=unomi.git
-scm.tag=unomi-root-${next.stable.version}
+scm.tag=unomi-root-{{ site.data.unomi.next.stable.version }}
and run mvn release:perform</code></pre>
</li>
<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 two (one for everything and the other for
KAR/features) for releases <= 1.2 and just one for versions >= 1.3.0
(because of changes in the Karaf plugins). Close the repositories and given a
meaningful comment when closing such as:<br>
- <strong>Apache Unomi ${next.stable.version} Release Candidate
1</strong>
+ <strong>Apache Unomi {{ site.data.unomi.next.stable.version }}
Release Candidate 1</strong>
</li>
</ol>
@@ -246,53 +246,53 @@ and run mvn release:perform</code></pre>
</li>
<li>
<pre class="alert alert-primary"><code>cd unomi-dev
-mkdir ${next.stable.version}</code></pre>
+mkdir {{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>
Copy all the Zip and Tarbars including ASC (but do not copy
the SHA1 or MD5 sum) files from:
- <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/${next.stable.version}/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/${next.stable.version}/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/"
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/</a>
and
- <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/${next.stable.version}/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/${next.stable.version}/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/{{
site.data.unomi.next.stable.version }}/"
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/{{
site.data.unomi.next.stable.version }}/</a>
using commands such as : <pre class="alert
alert-primary"><code>export REPO_ID=orgapacheunomi-1033
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/${next.stable.version}/unomi-${next.stable.version}.tar.gz
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/${next.stable.version}/unomi-${next.stable.version}.tar.gz.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/${next.stable.version}/unomi-${next.stable.version}.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/${next.stable.version}/unomi-${next.stable.version}.zip.asc</code></pre>
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/{{
site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/{{
site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/unomi-{{
site.data.unomi.next.stable.version }}.tar.gz
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/unomi-{{
site.data.unomi.next.stable.version }}.tar.gz.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/unomi-{{
site.data.unomi.next.stable.version }}.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/{{
site.data.unomi.next.stable.version }}/unomi-{{
site.data.unomi.next.stable.version }}.zip.asc</code></pre>
</li>
<li>
Rename the source and binary files to something shorter and
consistent with previous releases and generate
the SHA 512 checksum manually:
<pre class="alert alert-primary"><code>
-mv unomi-root-${next.stable.version}-source-release.zip
unomi-${next.stable.version}-src.zip
-mv unomi-root-${next.stable.version}-source-release.zip.asc
unomi-${next.stable.version}-src.zip.asc
-shasum -a 512 unomi-${next.stable.version}-src.zip >
unomi-${next.stable.version}-src.zip.sha512
+mv unomi-root-{{ site.data.unomi.next.stable.version }}-source-release.zip
unomi-{{ site.data.unomi.next.stable.version }}-src.zip
+mv unomi-root-{{ site.data.unomi.next.stable.version }}-source-release.zip.asc
unomi-{{ site.data.unomi.next.stable.version }}-src.zip.asc
+shasum -a 512 unomi-{{ site.data.unomi.next.stable.version }}-src.zip >
unomi-{{ site.data.unomi.next.stable.version }}-src.zip.sha512
-mv unomi-${next.stable.version}.zip unomi-${next.stable.version}-bin.zip
-mv unomi-${next.stable.version}.zip.asc
unomi-${next.stable.version}-bin.zip.asc
-shasum -a 512 unomi-${next.stable.version}-bin.zip >
unomi-${next.stable.version}-bin.zip.sha512
+mv unomi-{{ site.data.unomi.next.stable.version }}.zip unomi-{{
site.data.unomi.next.stable.version }}-bin.zip
+mv unomi-{{ site.data.unomi.next.stable.version }}.zip.asc unomi-{{
site.data.unomi.next.stable.version }}-bin.zip.asc
+shasum -a 512 unomi-{{ site.data.unomi.next.stable.version }}-bin.zip >
unomi-{{ site.data.unomi.next.stable.version }}-bin.zip.sha512
-mv unomi-${next.stable.version}.tar.gz unomi-${next.stable.version}-bin.tar.gz
-mv unomi-${next.stable.version}.tar.gz.asc
unomi-${next.stable.version}-bin.tar.gz.asc
-shasum -a 512 unomi-${next.stable.version}-bin.tar.gz >
unomi-${next.stable.version}-bin.tar.gz.sha512
+mv unomi-{{ site.data.unomi.next.stable.version }}.tar.gz unomi-{{
site.data.unomi.next.stable.version }}-bin.tar.gz
+mv unomi-{{ site.data.unomi.next.stable.version }}.tar.gz.asc unomi-{{
site.data.unomi.next.stable.version }}-bin.tar.gz.asc
+shasum -a 512 unomi-{{ site.data.unomi.next.stable.version }}-bin.tar.gz >
unomi-{{ site.data.unomi.next.stable.version }}-bin.tar.gz.sha512
</code></pre>
</li>
<li>
<pre class="alert alert-primary"><code>cd ..
-svn add ${next.stable.version}</code></pre>
+svn add {{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>
- <pre class="alert alert-primary"><code>svn commit -m "Apache
${next.stable.version} Release (for PMC voting)"</code></pre>
+ <pre class="alert alert-primary"><code>svn commit -m "Apache
{{ site.data.unomi.next.stable.version }} Release (for PMC voting)"</code></pre>
</li>
<li>Send out to the Unomi mailing list a mail to start the
voting process, see <a href="#mail-1">[1]</a></li>
<li>If the vote is refused or cancelled, peform the following
steps to restart the release process:
<ol>
<li>Drop the release in <a
href="https://repository.apache.org/#stagingRepositories";
target="_blank">Nexus</a></li>
<li>Remove the tag in Git:
- <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-${next.stable.version}
-git tag -d unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-{{ site.data.unomi.next.stable.version }}
+git tag -d unomi-root-{{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>Correct any problems in the source, make sure to
do them in master and cherry-pick them to the relevant branches</li>
<li>Reset all versions with the following command:
@@ -312,7 +312,7 @@ git tag -d unomi-root-${next.stable.version}</code></pre>
<ol>
<li>
Move the files uploaded to the unomi-dev repository to the
unomi-release repository by doing the following:
- <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/${next.stable.version}
https://dist.apache.org/repos/dist/release/unomi/${next.stable.version} -m
"Apache Unomi ${next.stable.version} Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/{{
site.data.unomi.next.stable.version }}
https://dist.apache.org/repos/dist/release/unomi/{{
site.data.unomi.next.stable.version }} -m "Apache Unomi {{
site.data.unomi.next.stable.version }} Release"</code></pre>
</li>
<li>
In JIRA mark the version as released and add a release date
@@ -350,7 +350,7 @@ git tag -d unomi-root-${next.stable.version}</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 ${next.stable.version} Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi {{ site.data.unomi.next.stable.version }} Release website update"
git push</code></pre>
</li>
</ol>
@@ -383,14 +383,14 @@ git push</code></pre>
You will now need to publish the new version of the manual
as downloadable resources
<pre class="alert alert-primary"><code>cd manual
cd target
-svn co https://dist.apache.org/repos/dist/release/unomi/${next.stable.version}
-mv unomi-manual-${doc.version}.pdf ${next.stable.version}
-mv unomi-manual-${doc.version}.pdf.asc ${next.stable.version}
-mv unomi-manual-${doc.version}.zip ${next.stable.version}
-mv unomi-manual-${doc.version}.pdf.sha512 ${next.stable.version}
-mv unomi-manual-${doc.version}.zip.asc ${next.stable.version}
-mv unomi-manual-${doc.version}.zip.sha512 ${next.stable.version}
-cd ${next.stable.version}
+svn co https://dist.apache.org/repos/dist/release/unomi/{{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.pdf {{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.pdf.asc {{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.zip {{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.pdf.sha512 {{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.zip.asc {{
site.data.unomi.next.stable.version }}
+mv unomi-manual-{{ site.data.unomi.doc.version }}.zip.sha512 {{
site.data.unomi.next.stable.version }}
+cd {{ site.data.unomi.next.stable.version }}
svn add unomi-manual*
svn commit -m "Update Unomi manual packages"</code></pre>
</li>
@@ -405,7 +405,7 @@ svn commit -m "Update Unomi manual packages"</code></pre>
<ol>
<li>
Checkout the tagged version:
- <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-{{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>
Change to the Docker directory. Make sure you have docker
running locally (start Docker Desktop for
@@ -423,8 +423,8 @@ mvn docker:push</code></pre>
<h3 id="rollback">Rollback</h3>
<ol>
<li>Delete the tag:
- <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-${next.stable.version}
-git tag --delete unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-{{ site.data.unomi.next.stable.version }}
+git tag --delete unomi-root-{{ site.data.unomi.next.stable.version
}}</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -474,11 +474,11 @@ git push origin -f</code></pre>
<h6 id="mail-1" class="pt-3">[1] Mail template for the Unomi PMC
vote:</h6>
<pre class="alert alert-primary"><code>
-Subject: [VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
+Subject: [VOTE] Apache Unomi {{ site.data.unomi.next.stable.version }} release
[TAKE2]
Body:
Hi all,
-I submit Apache Unomi ${next.stable.version} release [TAKE2] to your vote.
+I submit Apache Unomi {{ site.data.unomi.next.stable.version }} release
[TAKE2] to your vote.
The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
@@ -492,18 +492,18 @@ Staging Repository:
You can find the sources here :
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip
+unomi/unomi-root/{{ site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip>*
+unomi/unomi-root/{{ site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/${next.stable.version}/
+unomi/unomi/{{ site.data.unomi.next.stable.version }}/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/${next.stable.version}/>*
+unomi/unomi/{{ site.data.unomi.next.stable.version }}/>*
Git tag:
-unomi-root-${next.stable.version}
+unomi-root-{{ site.data.unomi.next.stable.version }}
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -525,7 +525,7 @@ Regards
<h6 id="mail-2" class="pt-3">[2] Mail template for the results of
the Unomi PMC vote:</h6>
<pre class="alert alert-primary"><code>
-Subject: [RESULT][VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi {{ site.data.unomi.next.stable.version }}
release [TAKE2]
Body:
Hi,
@@ -545,7 +545,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi ${next.stable.version} is approved by the team.
+The proposal to release Unomi {{ site.data.unomi.next.stable.version }} is
approved by the team.
Thanks,
John Doe 1
@@ -553,10 +553,10 @@ John Doe 1
<h6 id="mail-3" class="pt-3">[3] Announce mailing list
template:</h6>
<pre class="alert alert-primary"><code>
-Subject : [ANNOUNCE] Apache Unomi ${next.stable.version} Release
+Subject : [ANNOUNCE] Apache Unomi {{ site.data.unomi.next.stable.version }}
Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi ${next.stable.version}.
+Unomi {{ site.data.unomi.next.stable.version }}.
Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -570,10 +570,10 @@ More details regarding Apache Unomi can be found here:
http://unomi.apache.org/
The release artifacts can be downloaded here:
-https://dist.apache.org/repos/dist/release/incubator/unomi/${next.stable.version}/
+https://dist.apache.org/repos/dist/release/incubator/unomi/{{
site.data.unomi.next.stable.version }}/
All JIRAs completed for this release are tagged with 'FixVersion =
-${next.stable.version}'; the JIRA release notes can be found here:
+{{ site.data.unomi.next.stable.version }}'; the JIRA release notes can be
found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
version=12338361
diff --git a/src/main/webapp/contribute/release-guide.html
b/src/main/webapp/contribute/release-guide.html
index 20b847e..20642d7 100644
--- a/src/main/webapp/contribute/release-guide.html
+++ b/src/main/webapp/contribute/release-guide.html
@@ -137,12 +137,12 @@ gpg --verify test.txt.asc test.txt
<li>
Update all JIRAs, close the ones that are still not closed,
review tickets that can be closed, postpone to another release tickets that are
not managed now.
You can use this JIRA page: <a
href="https://issues.apache.org/jira/projects/UNOMI?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased";>Unomi
JIRA releases</a>.
- Then review the list of tickets that need to be updated,
also additionally you can check the list of commits since previous release and
insure they are closed using fix version: ${next.stable.version}.
- Ideally all tickets listed for version:
${next.stable.version} should be closed or moved to the next version in case
they are not finished/started.
+ Then review the list of tickets that need to be updated,
also additionally you can check the list of commits since previous release and
insure they are closed using fix version: {{
site.data.unomi.next.stable.version }}.
+ Ideally all tickets listed for version: {{
site.data.unomi.next.stable.version }} should be closed or moved to the next
version in case they are not finished/started.
</li>
<li>
Then you can also generate a release notes automatically
using: <a
href="https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12319220&version=12350150";>JIRA
release note</a>,
- By choosing the version: ${next.stable.version}. It will
be useful for linking the release notes in the voting mail.
+ By choosing the version: {{
site.data.unomi.next.stable.version }}. It will be useful for linking the
release notes in the voting mail.
</li>
</ol>
@@ -162,13 +162,13 @@ gpg --verify test.txt.asc test.txt
<a
href="https://www.apache.org/dev/publishing-maven-artifacts.html";
target="_blank">https://www.apache.org/dev/publishing-maven-artifacts.html</a>
and <a
href="https://maven.apache.org/guides/mini/guide-encryption.html#How_to_encrypt_server_passwords";
target="_blank">https://maven.apache.org/guides/mini/guide-encryption.html#How_to_encrypt_server_passwords</a>
</li>
<li>Launch the first build script using.
- <pre class="alert alert-primary"><code>./release-stage-1.sh
${next.stable.version} BRANCH_NAME</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-1.sh {{
site.data.unomi.next.stable.version }} BRANCH_NAME</code></pre>
where BRANCH_NAME is the branch you want to release (It must
be created first if it doesn't exist !).<br>
<strong>This step will generate staging artifacts onto the
<a href="https://repository.apache.org/#stagingRepositories";>Apache Nexus</a>,
if at the end of the script the
artefacts are not there, something bad happened in the
script execution.</strong>
</li>
<li>Check that there are no JARs or ZIP files in the source
code, you can do this by looking at the generated RAT report here :
- <pre class="alert alert-primary"><code>less
target/unomi-root-${next.development.version}.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-{{ site.data.unomi.next.development.version
}}.rat</code></pre>
</li>
<li>Check that the KEYS file only contains signatures with
@apache.org addresses (if there are non @apache.org don’t remove them because
they have
been used to sign older releases)
@@ -191,19 +191,19 @@ gpg: signing failed: Inappropriate ioctl for
device</code></pre>
<li>If something fails, make sure you first drop the staging
repository created here: <a
href="https://repository.apache.org/#stagingRepositories";
target="_blank">https://repository.apache.org/#stagingRepositories</a>.<br>
If you need to relaunch the <code>release:perform</code> and don’t have a
release.properties, create a <code>release.properties</code> file with the
following contents:
<pre class="alert
alert-primary"><code>scm.url=scm:git:https://gitbox.apache.org/repos/asf?p=unomi.git
-scm.tag=unomi-root-${next.stable.version}
+scm.tag=unomi-root-{{ site.data.unomi.next.stable.version }}
and run mvn release:perform</code></pre>
</li>
<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 two (one for everything and the other for
KAR/features) for releases <= 1.2 and just one for versions >= 1.3.0
(because of changes in the Karaf plugins). Close the repositories and given a
meaningful comment when closing such as:<br>
- <strong>Apache Unomi ${next.stable.version} Release Candidate
1</strong>. If no artefact related to Unomi is present, something wrong
happened in <code>release-stage-1.sh</code>.
+ <strong>Apache Unomi {{ site.data.unomi.next.stable.version }}
Release Candidate 1</strong>. If no artefact related to Unomi is present,
something wrong happened in <code>release-stage-1.sh</code>.
</li>
</ol>
<h3 id="publish-vote">Vote</h3>
<ol>
<li>Launch the second stage of the release script
- <pre class="alert alert-primary"><code>./release-stage-2.sh
${next.stable.version} orgapacheunomi-NEXUS-UNOMI-ID</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-2.sh {{
site.data.unomi.next.stable.version }}
orgapacheunomi-NEXUS-UNOMI-ID</code></pre>
where NEXUS-UNOMI-ID is the ID generated by Nexus for the
staging artifacts.
</li>
<li>Send out to the Unomi mailing list a mail to start the
voting process, see <a href="#mail-1">[1]</a></li>
@@ -211,8 +211,8 @@ and run mvn release:perform</code></pre>
<ol>
<li>Drop the release in <a
href="https://repository.apache.org/#stagingRepositories";
target="_blank">Nexus</a></li>
<li>Remove the tag in Git:
- <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-${next.stable.version}
-git tag -d unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-{{ site.data.unomi.next.stable.version }}
+git tag -d unomi-root-{{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>Correct any problems in the source, make sure to
do them in master and cherry-pick them to the relevant branches</li>
<li>Reset all versions with the following command:
@@ -232,7 +232,7 @@ git tag -d unomi-root-${next.stable.version}</code></pre>
<ol>
<li>
Move the files uploaded to the unomi-dev repository to the
unomi-release repository by doing the following:
- <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/${next.stable.version}
https://dist.apache.org/repos/dist/release/unomi/${next.stable.version} -m
"Apache Unomi ${next.stable.version} Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/{{
site.data.unomi.next.stable.version }}
https://dist.apache.org/repos/dist/release/unomi/{{
site.data.unomi.next.stable.version }} -m "Apache Unomi {{
site.data.unomi.next.stable.version }} Release"</code></pre>
</li>
<li>
In JIRA mark the version as released and add a release date
@@ -280,7 +280,7 @@ mvn install scm-publish:publish-scm
-Dusername=YOUR_APACHE_USERNAME -Dpassword=Y
</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 ${next.stable.version} Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi {{ site.data.unomi.next.stable.version }} Release website update"
git push</code></pre>
</li>
</ol>
@@ -289,7 +289,7 @@ git push</code></pre>
<ol>
<li>
- Launch <pre class="alert
alert-primary"><code>./generate-site.sh ${doc.version}
${next.stable.version}</code></pre> from the project's
+ Launch <pre class="alert
alert-primary"><code>./generate-site.sh {{ site.data.unomi.doc.version }} {{
site.data.unomi.next.stable.version }}</code></pre> from the project's
root directory.
</li>
<li>Check the generated site by opening
<code>target/staging/manual/index.html</code>
@@ -297,7 +297,7 @@ git push</code></pre>
</li>
<li>
Upload the site modification by using:
- <pre class="alert
alert-primary"><code>./generate-site-and-upload.sh ${doc.version}
${next.stable.version} APACHE_LDAP_USERNAME APACHE_LDAP_PASSWORD</code></pre>
+ <pre class="alert
alert-primary"><code>./generate-site-and-upload.sh {{
site.data.unomi.doc.version }} {{ site.data.unomi.next.stable.version }}
APACHE_LDAP_USERNAME APACHE_LDAP_PASSWORD</code></pre>
</li>
<li>
Go back to the site project and make sure you update the
documentation page to link to the proper
@@ -310,7 +310,7 @@ git push</code></pre>
<ol>
<li>
Checkout the tagged version:
- <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-{{ site.data.unomi.next.stable.version }}</code></pre>
</li>
<li>
Change to the Docker directory. Make sure you have docker
running locally (start Docker Desktop for
@@ -328,8 +328,8 @@ mvn docker:push</code></pre>
<h3 id="rollback">Rollback</h3>
<ol>
<li>Delete the tag:
- <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-${next.stable.version}
-git tag --delete unomi-root-${next.stable.version}</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-{{ site.data.unomi.next.stable.version }}
+git tag --delete unomi-root-{{ site.data.unomi.next.stable.version
}}</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -379,11 +379,11 @@ git push origin -f</code></pre>
<h6 id="mail-1" class="pt-3">[1] Mail template for the Unomi PMC
vote:</h6>
<pre class="alert alert-primary"><code>
-Subject: [VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
+Subject: [VOTE] Apache Unomi {{ site.data.unomi.next.stable.version }} release
[TAKE2]
Body:
Hi all,
-I submit Apache Unomi ${next.stable.version} release [TAKE2] to your vote.
+I submit Apache Unomi {{ site.data.unomi.next.stable.version }} release
[TAKE2] to your vote.
The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
@@ -397,18 +397,18 @@ Staging Repository:
You can find the sources here :
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip
+unomi/unomi-root/{{ site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip>*
+unomi/unomi-root/{{ site.data.unomi.next.stable.version }}/unomi-root-{{
site.data.unomi.next.stable.version }}-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/${next.stable.version}/
+unomi/unomi/{{ site.data.unomi.next.stable.version }}/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/${next.stable.version}/>*
+unomi/unomi/{{ site.data.unomi.next.stable.version }}/>*
Git tag:
-unomi-root-${next.stable.version}
+unomi-root-{{ site.data.unomi.next.stable.version }}
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -430,7 +430,7 @@ Regards
<h6 id="mail-2" class="pt-3">[2] Mail template for the results of
the Unomi PMC vote:</h6>
<pre class="alert alert-primary"><code>
-Subject: [RESULT][VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi {{ site.data.unomi.next.stable.version }}
release [TAKE2]
Body:
Hi,
@@ -450,7 +450,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi ${next.stable.version} is approved by the team.
+The proposal to release Unomi {{ site.data.unomi.next.stable.version }} is
approved by the team.
Thanks,
John Doe 1
@@ -458,10 +458,10 @@ John Doe 1
<h6 id="mail-3" class="pt-3">[3] Announce mailing list
template:</h6>
<pre class="alert alert-primary"><code>
-Subject : [ANNOUNCE] Apache Unomi ${next.stable.version} Release
+Subject : [ANNOUNCE] Apache Unomi {{ site.data.unomi.next.stable.version }}
Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi ${next.stable.version}.
+Unomi {{ site.data.unomi.next.stable.version }}.
Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -475,10 +475,10 @@ More details regarding Apache Unomi can be found here:
http://unomi.apache.org/
The release artifacts can be downloaded here:
-https://dist.apache.org/repos/dist/release/incubator/unomi/${next.stable.version}/
+https://dist.apache.org/repos/dist/release/incubator/unomi/{{
site.data.unomi.next.stable.version }}/
All JIRAs completed for this release are tagged with 'FixVersion =
-${next.stable.version}'; the JIRA release notes can be found here:
+{{ site.data.unomi.next.stable.version }}'; the JIRA release notes can be
found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
version=12338361
diff --git a/src/main/webapp/documentation.html
b/src/main/webapp/documentation.html
index 1aa727a..396441b 100644
--- a/src/main/webapp/documentation.html
+++ b/src/main/webapp/documentation.html
@@ -31,7 +31,7 @@ layout: default
<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-warning"><i class="fas
fa-circle"></i> Unstable</strong>
- <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">${latest.development.version}</span></h3>
+ <h3 class="mb-0 text-dark">Unomi <span class="text-muted">{{
site.data.unomi.latest.development.version }}</span></h3>
<div class="mb-1 text-muted">In development</div>
<p class="card-text">
<a href="manual/latest/index.html">online</a><br>
