Author: dgriffon
Date: Sun Sep 3 11:47:53 2023
New Revision: 1912071
URL: http://svn.apache.org/viewvc?rev=1912071&view=rev
Log:
[scm-publish] Updating Unomi website
Modified:
unomi/website/connectors.html
unomi/website/contribute/manual-release-guide.html
unomi/website/contribute/release-guide.html
unomi/website/documentation.html
unomi/website/download.html
unomi/website/index.html
Modified: unomi/website/connectors.html
URL:
http://svn.apache.org/viewvc/unomi/website/connectors.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/connectors.html (original)
+++ unomi/website/connectors.html Sun Sep 3 11:47:53 2023
@@ -101,7 +101,7 @@
<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">2.4.0-SNAPSHOT</span></h3>
+ <h3 class="mb-0 text-dark">MailChimp <span
class="text-muted">2.5.0-SNAPSHOT</span></h3>
<div class="mb-1 text-muted">In development</div>
<p class="card-text">
<a href="manual/latest/index.html">Download</a><br>
Modified: unomi/website/contribute/manual-release-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/manual-release-guide.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/contribute/manual-release-guide.html (original)
+++ unomi/website/contribute/manual-release-guide.html Sun Sep 3 11:47:53 2023
@@ -213,12 +213,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: 2.4.0.
- Ideally all tickets listed for version: 2.4.0 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: 2.5.0.
+ Ideally all tickets listed for version: 2.5.0 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: 2.4.0. It will be useful for
linking the release notes in the voting mail.
+ By choosing the version: 2.5.0. It will be useful for
linking the release notes in the voting mail.
</li>
</ol>
@@ -231,12 +231,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-2.3.x
+git checkout unomi-master
</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-2.3.x
+git checkout -b unomi-master
</code></pre>
</li>
</ol>
@@ -253,7 +253,7 @@ git checkout -b unomi-2.3.x
<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-2.4.0-SNAPSHOT.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-2.5.0-SNAPSHOT.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)
@@ -279,11 +279,11 @@ gpg: signing failed: Inappropriate ioctl
</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-2.4.0-SNAPSHOT-source-release.zip.asc
unomi-root-2.4.0-SNAPSHOT-source-release.zip
-shasum -a 512 unomi-root-2.4.0-SNAPSHOT-source-release.zip
-cat unomi-root-2.4.0-SNAPSHOT-source-release.zip.sha512
-unzip unomi-root-2.4.0-SNAPSHOT-source-release.zip
-cd unomi-root-2.4.0-SNAPSHOT
+gpg --verify unomi-root-2.5.0-SNAPSHOT-source-release.zip.asc
unomi-root-2.5.0-SNAPSHOT-source-release.zip
+shasum -a 512 unomi-root-2.5.0-SNAPSHOT-source-release.zip
+cat unomi-root-2.5.0-SNAPSHOT-source-release.zip.sha512
+unzip unomi-root-2.5.0-SNAPSHOT-source-release.zip
+cd unomi-root-2.5.0-SNAPSHOT
mvn clean install
popd</code></pre>
to check that the packaged source build properly
@@ -306,12 +306,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-2.4.0
+scm.tag=unomi-root-2.5.0
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 2.4.0 Release Candidate 1</strong>
+ <strong>Apache Unomi 2.5.0 Release Candidate 1</strong>
</li>
</ol>
@@ -322,53 +322,53 @@ and run mvn release:perform</code></pre>
</li>
<li>
<pre class="alert alert-primary"><code>cd unomi-dev
-mkdir 2.4.0</code></pre>
+mkdir 2.5.0</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/2.4.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.4.0/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.5.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.5.0/</a>
and
- <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.4.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.4.0/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.5.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.5.0/</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/2.4.0/unomi-root-2.4.0-source-release.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.4.0/unomi-root-2.4.0-source-release.zip.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.4.0/unomi-2.4.0.tar.gz
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.4.0/unomi-2.4.0.tar.gz.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.4.0/unomi-2.4.0.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.4.0/unomi-2.4.0.zip.asc</code></pre>
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.5.0/unomi-2.5.0.tar.gz
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.5.0/unomi-2.5.0.tar.gz.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.5.0/unomi-2.5.0.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.5.0/unomi-2.5.0.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-2.4.0-source-release.zip unomi-2.4.0-src.zip
-mv unomi-root-2.4.0-source-release.zip.asc unomi-2.4.0-src.zip.asc
-shasum -a 512 unomi-2.4.0-src.zip > unomi-2.4.0-src.zip.sha512
-
-mv unomi-2.4.0.zip unomi-2.4.0-bin.zip
-mv unomi-2.4.0.zip.asc unomi-2.4.0-bin.zip.asc
-shasum -a 512 unomi-2.4.0-bin.zip > unomi-2.4.0-bin.zip.sha512
-
-mv unomi-2.4.0.tar.gz unomi-2.4.0-bin.tar.gz
-mv unomi-2.4.0.tar.gz.asc unomi-2.4.0-bin.tar.gz.asc
-shasum -a 512 unomi-2.4.0-bin.tar.gz > unomi-2.4.0-bin.tar.gz.sha512
+mv unomi-root-2.5.0-source-release.zip unomi-2.5.0-src.zip
+mv unomi-root-2.5.0-source-release.zip.asc unomi-2.5.0-src.zip.asc
+shasum -a 512 unomi-2.5.0-src.zip > unomi-2.5.0-src.zip.sha512
+
+mv unomi-2.5.0.zip unomi-2.5.0-bin.zip
+mv unomi-2.5.0.zip.asc unomi-2.5.0-bin.zip.asc
+shasum -a 512 unomi-2.5.0-bin.zip > unomi-2.5.0-bin.zip.sha512
+
+mv unomi-2.5.0.tar.gz unomi-2.5.0-bin.tar.gz
+mv unomi-2.5.0.tar.gz.asc unomi-2.5.0-bin.tar.gz.asc
+shasum -a 512 unomi-2.5.0-bin.tar.gz > unomi-2.5.0-bin.tar.gz.sha512
</code></pre>
</li>
<li>
<pre class="alert alert-primary"><code>cd ..
-svn add 2.4.0</code></pre>
+svn add 2.5.0</code></pre>
</li>
<li>
- <pre class="alert alert-primary"><code>svn commit -m "Apache
2.4.0 Release (for PMC voting)"</code></pre>
+ <pre class="alert alert-primary"><code>svn commit -m "Apache
2.5.0 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-2.4.0
-git tag -d unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-2.5.0
+git tag -d unomi-root-2.5.0</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:
@@ -388,7 +388,7 @@ git tag -d unomi-root-2.4.0</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/2.4.0
https://dist.apache.org/repos/dist/release/unomi/2.4.0 -m "Apache Unomi 2.4.0
Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/2.5.0
https://dist.apache.org/repos/dist/release/unomi/2.5.0 -m "Apache Unomi 2.5.0
Release"</code></pre>
</li>
<li>
In JIRA mark the version as released and add a release date
@@ -426,7 +426,7 @@ git tag -d unomi-root-2.4.0</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.4.0 Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.5.0 Release website update"
git push</code></pre>
</li>
</ol>
@@ -459,14 +459,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/2.4.0
-mv unomi-manual-2_3_x.pdf 2.4.0
-mv unomi-manual-2_3_x.pdf.asc 2.4.0
-mv unomi-manual-2_3_x.zip 2.4.0
-mv unomi-manual-2_3_x.pdf.sha512 2.4.0
-mv unomi-manual-2_3_x.zip.asc 2.4.0
-mv unomi-manual-2_3_x.zip.sha512 2.4.0
-cd 2.4.0
+svn co https://dist.apache.org/repos/dist/release/unomi/2.5.0
+mv unomi-manual-master.pdf 2.5.0
+mv unomi-manual-master.pdf.asc 2.5.0
+mv unomi-manual-master.zip 2.5.0
+mv unomi-manual-master.pdf.sha512 2.5.0
+mv unomi-manual-master.zip.asc 2.5.0
+mv unomi-manual-master.zip.sha512 2.5.0
+cd 2.5.0
svn add unomi-manual*
svn commit -m "Update Unomi manual packages"</code></pre>
</li>
@@ -481,7 +481,7 @@ svn commit -m "Update Unomi manual packa
<ol>
<li>
Checkout the tagged version:
- <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.5.0</code></pre>
</li>
<li>
Change to the Docker directory. Make sure you have docker
running locally (start Docker Desktop for
@@ -499,8 +499,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-2.4.0
-git tag --delete unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-2.5.0
+git tag --delete unomi-root-2.5.0</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -550,11 +550,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 2.4.0 release [TAKE2]
+Subject: [VOTE] Apache Unomi 2.5.0 release [TAKE2]
Body:
Hi all,
-I submit Apache Unomi 2.4.0 release [TAKE2] to your vote.
+I submit Apache Unomi 2.5.0 release [TAKE2] to your vote.
The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
@@ -568,18 +568,18 @@ Staging Repository:
You can find the sources here :
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.4.0/unomi-root-2.4.0-source-release.zip
+unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.4.0/unomi-root-2.4.0-source-release.zip>*
+unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.4.0/
+unomi/unomi/2.5.0/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.4.0/>*
+unomi/unomi/2.5.0/>*
Git tag:
-unomi-root-2.4.0
+unomi-root-2.5.0
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -601,7 +601,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 2.4.0 release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi 2.5.0 release [TAKE2]
Body:
Hi,
@@ -621,7 +621,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi 2.4.0 is approved by the team.
+The proposal to release Unomi 2.5.0 is approved by the team.
Thanks,
John Doe 1
@@ -629,10 +629,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 2.4.0 Release
+Subject : [ANNOUNCE] Apache Unomi 2.5.0 Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi 2.4.0.
+Unomi 2.5.0.
Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -646,10 +646,10 @@ More details regarding Apache Unomi can
http://unomi.apache.org/
The release artifacts can be downloaded here:
-https://dist.apache.org/repos/dist/release/incubator/unomi/2.4.0/
+https://dist.apache.org/repos/dist/release/incubator/unomi/2.5.0/
All JIRAs completed for this release are tagged with 'FixVersion =
-2.4.0'; the JIRA release notes can be found here:
+2.5.0'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
version=12338361
Modified: unomi/website/contribute/release-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/release-guide.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/contribute/release-guide.html (original)
+++ unomi/website/contribute/release-guide.html Sun Sep 3 11:47:53 2023
@@ -213,12 +213,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: 2.4.0.
- Ideally all tickets listed for version: 2.4.0 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: 2.5.0.
+ Ideally all tickets listed for version: 2.5.0 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: 2.4.0. It will be useful for
linking the release notes in the voting mail.
+ By choosing the version: 2.5.0. It will be useful for
linking the release notes in the voting mail.
</li>
</ol>
@@ -238,13 +238,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
2.4.0 BRANCH_NAME</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-1.sh
2.5.0 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-2.4.0-SNAPSHOT.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-2.5.0-SNAPSHOT.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)
@@ -267,19 +267,19 @@ gpg: signing failed: Inappropriate ioctl
<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-2.4.0
+scm.tag=unomi-root-2.5.0
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 2.4.0 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 2.5.0 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
2.4.0 orgapacheunomi-NEXUS-UNOMI-ID</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-2.sh
2.5.0 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>
@@ -287,8 +287,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-2.4.0
-git tag -d unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-2.5.0
+git tag -d unomi-root-2.5.0</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:
@@ -308,7 +308,7 @@ git tag -d unomi-root-2.4.0</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/2.4.0
https://dist.apache.org/repos/dist/release/unomi/2.4.0 -m "Apache Unomi 2.4.0
Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/2.5.0
https://dist.apache.org/repos/dist/release/unomi/2.5.0 -m "Apache Unomi 2.5.0
Release"</code></pre>
</li>
<li>
In JIRA mark the version as released and add a release date
@@ -356,7 +356,7 @@ mvn install scm-publish:publish-scm -Dus
</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.4.0 Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.5.0 Release website update"
git push</code></pre>
</li>
</ol>
@@ -365,7 +365,7 @@ git push</code></pre>
<ol>
<li>
- Launch <pre class="alert
alert-primary"><code>./generate-site.sh 2_3_x 2.4.0</code></pre> from the
project's
+ Launch <pre class="alert
alert-primary"><code>./generate-site.sh master 2.5.0</code></pre> from the
project's
root directory.
</li>
<li>Check the generated site by opening
<code>target/staging/manual/index.html</code>
@@ -373,7 +373,7 @@ git push</code></pre>
</li>
<li>
Upload the site modification by using:
- <pre class="alert
alert-primary"><code>./generate-site-and-upload.sh 2_3_x 2.4.0
APACHE_LDAP_USERNAME APACHE_LDAP_PASSWORD</code></pre>
+ <pre class="alert
alert-primary"><code>./generate-site-and-upload.sh master 2.5.0
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
@@ -386,7 +386,7 @@ git push</code></pre>
<ol>
<li>
Checkout the tagged version:
- <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.5.0</code></pre>
</li>
<li>
Change to the Docker directory. Make sure you have docker
running locally (start Docker Desktop for
@@ -404,8 +404,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-2.4.0
-git tag --delete unomi-root-2.4.0</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-2.5.0
+git tag --delete unomi-root-2.5.0</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -455,11 +455,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 2.4.0 release [TAKE2]
+Subject: [VOTE] Apache Unomi 2.5.0 release [TAKE2]
Body:
Hi all,
-I submit Apache Unomi 2.4.0 release [TAKE2] to your vote.
+I submit Apache Unomi 2.5.0 release [TAKE2] to your vote.
The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
@@ -473,18 +473,18 @@ Staging Repository:
You can find the sources here :
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.4.0/unomi-root-2.4.0-source-release.zip
+unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.4.0/unomi-root-2.4.0-source-release.zip>*
+unomi/unomi-root/2.5.0/unomi-root-2.5.0-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.4.0/
+unomi/unomi/2.5.0/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.4.0/>*
+unomi/unomi/2.5.0/>*
Git tag:
-unomi-root-2.4.0
+unomi-root-2.5.0
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -506,7 +506,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 2.4.0 release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi 2.5.0 release [TAKE2]
Body:
Hi,
@@ -526,7 +526,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi 2.4.0 is approved by the team.
+The proposal to release Unomi 2.5.0 is approved by the team.
Thanks,
John Doe 1
@@ -534,10 +534,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 2.4.0 Release
+Subject : [ANNOUNCE] Apache Unomi 2.5.0 Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi 2.4.0.
+Unomi 2.5.0.
Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -551,10 +551,10 @@ More details regarding Apache Unomi can
http://unomi.apache.org/
The release artifacts can be downloaded here:
-https://dist.apache.org/repos/dist/release/incubator/unomi/2.4.0/
+https://dist.apache.org/repos/dist/release/incubator/unomi/2.5.0/
All JIRAs completed for this release are tagged with 'FixVersion =
-2.4.0'; the JIRA release notes can be found here:
+2.5.0'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
version=12338361
Modified: unomi/website/documentation.html
URL:
http://svn.apache.org/viewvc/unomi/website/documentation.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/documentation.html (original)
+++ unomi/website/documentation.html Sun Sep 3 11:47:53 2023
@@ -107,7 +107,7 @@
<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">2.4.0-SNAPSHOT</span></h3>
+ <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">2.5.0-SNAPSHOT</span></h3>
<div class="mb-1 text-muted">In development</div>
<p class="card-text">
<a href="manual/latest/index.html">online</a><br>
Modified: unomi/website/download.html
URL:
http://svn.apache.org/viewvc/unomi/website/download.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/download.html (original)
+++ unomi/website/download.html Sun Sep 3 11:47:53 2023
@@ -87,24 +87,24 @@
<div class="card flex-md-row mb-2 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> Latest release</strong>
- <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">2.3.0</span></h3>
+ <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">2.4.0</span></h3>
<div class="mb-1 text-muted">April 4th, 2023</div>
<p class="card-text mb-auto">
Binary Distribution :
- <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.3.0/unomi-2.3.0-bin.tar.gz";>tar.gz</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.tar.gz.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.tar.gz.sha512";>SHA512</a>]
-
- <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.3.0/unomi-2.3.0-bin.zip";>zip</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.zip.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.zip.sha512";>SHA512</a>]
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.4.0/unomi-2.4.0-bin.tar.gz";>tar.gz</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-bin.tar.gz.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-bin.tar.gz.sha512";>SHA512</a>]
-
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.4.0/unomi-2.4.0-bin.zip";>zip</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-bin.zip.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-bin.zip.sha512";>SHA512</a>]
</p>
<p class="card-text mb-auto">
Source Distribution :
- <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.3.0/unomi-2.3.0-src.zip";>zip</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-src.zip.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.3.0/unomi-2.3.0-src.zip.sha512";>SHA512</a>]
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.4.0/unomi-2.4.0-src.zip";>zip</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-src.zip.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.4.0/unomi-2.4.0-src.zip.sha512";>SHA512</a>]
</p>
- <a class="btn btn-outline-dark mt-3"
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12352651";
role="button" target="_blank">Release notes »</a>
+ <a class="btn btn-outline-dark mt-3"
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12353174";
role="button" target="_blank">Release notes »</a>
</div>
</div>
</div>
@@ -172,7 +172,7 @@
</code>
<br>
<code>
- % gpg --verify unomi-2.3.0-bin.tar.gz.asc
unomi-2.3.0-bin.tar.gz
+ % gpg --verify unomi-2.4.0-bin.tar.gz.asc
unomi-2.4.0-bin.tar.gz
</code>
</p>
</div>
@@ -196,6 +196,33 @@
</thead>
<tbody>
<tr>
+ <td>2.3.0</td>
+ <td><a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.tar.gz";>tar.gz</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.tar.gz.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.tar.gz.sha512";>SHA512</a>]<br>
+ <a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.zip";>zip</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.zip.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-bin.zip.sha512";>SHA512</a>]
+ </td>
+ <td>
+ <a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-src.zip";>zip</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-src.zip.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.3.0/unomi-2.3.0-src.zip.sha512";>SHA512</a>]
+ </td>
+ <td><a target="_blank"
+
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12352651";>Release
+ Notes</a></td>
+ </tr>
+ <tr>
<td>2.2.0</td>
<td><a target="_blank"
href="https://archive.apache.org/dist/unomi/2.2.0/unomi-2.2.0-bin.tar.gz";>tar.gz</a>
Modified: unomi/website/index.html
URL:
http://svn.apache.org/viewvc/unomi/website/index.html?rev=1912071&r1=1912070&r2=1912071&view=diff
==============================================================================
--- unomi/website/index.html (original)
+++ unomi/website/index.html Sun Sep 3 11:47:53 2023
@@ -79,25 +79,28 @@
</header>
<main>
- <div class="container-fluid product pt-5 pb-5 mx-auto">
- <div class="row pt-5 pb-5">
- <div class="container">
+ <div class="container-fluid product pt-5 pb-5 mx-auto">
+ <div class="row pt-5 pb-5">
+ <div class="container">
<div class="col pt-5 mx-auto text-left">
- <h1 class="display-5">Apache Unomi™: The Open Source
Customer Data Platform</h1>
- <p class="lead">Apache Unomi™ (pronounced "You know me")
is a Java Open Source customer data platform, a Java server designed to manage
customers, leads and visitors data and help personalize customers experiences
while also offering features to respect visitor privacy rules (such as GDPR)</p>
- <div class="pt-4">
- <a class="btn btn-primary btn-lg"
href="get-started.html">Learn more</a>
- <a class="btn btn-primary btn-lg"
href="download.html">Download</a>
- </div>
+ <h1 class="display-5">Apache Unomi™: The Open Source
Customer Data Platform</h1>
+ <p class="lead">Apache Unomi™ (pronounced "You know me")
is a Java Open Source customer data
+ platform, a Java server designed to manage customers,
leads and visitors data and help personalize
+ customers experiences while also offering features to
respect visitor privacy rules (such as
+ GDPR)</p>
+ <div class="pt-4">
+ <a class="btn btn-primary btn-lg"
href="get-started.html">Learn more</a>
+ <a class="btn btn-primary btn-lg"
href="download.html">Download</a>
+ </div>
</div>
- </div>
</div>
- </div>
+ </div>
+</div>
- <!-- Marketing messaging and featurettes
- ================================================== -->
- <!-- Wrap the rest of the page in another container to center all the
content. -->
+<!-- Marketing messaging and featurettes
+================================================== -->
+<!-- Wrap the rest of the page in another container to center all the content.
-->
<div class="container marketing pt-5">
@@ -105,6 +108,62 @@
<div class="row">
<div class="col-lg-6 pl-5">
+ <h3>Version 2.4.0 released!</h3>
+ <h4>Changes in 2.4.0 (since 2.3.0)</h4>
+ <h5> Bug Fix
+ </h5>
+ <ul>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-784'>UNOMI-784</a>] - Timeout
on updateByQuery
+ request such as scoring update
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-788'>UNOMI-788</a>] - remove
OGNL warning when
+ evaluating missing properties
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-792'>UNOMI-792</a>] - Log
error should be
+ warning
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-796'>UNOMI-796</a>] - Add
log4j conf + env
+ variable to set SchemaService log level
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-800'>UNOMI-800</a>] - Example
tracker page
+ view event is rejected
+ </li>
+ </ul>
+
+ <h5> Improvement
+ </h5>
+ <ul>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-787'>UNOMI-787</a>] - Improve
migration script
+ from unomi 1.x to 2.x to take target.properties.path into
account
+ </li>
+ </ul>
+
+ <h5> Task
+ </h5>
+ <ul>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-789'>UNOMI-789</a>] - Update
json schema
+ validator library
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-790'>UNOMI-790</a>] - Clean
+ properties.attributes
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-791'>UNOMI-791</a>] - Make
sessionId optional
+ for events
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-795'>UNOMI-795</a>] - Fix the
use of jekyll
+ for unomi-site
+ </li>
+ <li>[<a
href='https://issues.apache.org/jira/browse/UNOMI-799'>UNOMI-799</a>] - Upgrade
nodejs version
+ to 16
+ </li>
+ </ul>
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-6 my-auto mx-auto">
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
+
+ <hr class="featurette-divider"><div class="row">
+ <div class="col-lg-6 pl-5">
<h3>Version 1.9.1 released!</h3>
<h4>Changes in 1.9.1 (since 1.9.0)</h4>
<ul>
@@ -120,6 +179,7 @@
<hr class="featurette-divider">
<div class="row">
+
<div class="col-lg-6 pl-5">
<h3>Version 2.3.0 released!</h3>
<h4>Changes in 2.3.0 (since 2.2.0)</h4>
@@ -164,7 +224,9 @@
<h4>Changes in 2.2.0 (since 2.1.0)</h4>
<ul>
<li>Reduced the number of ElasticSearch indices</li>
- <li>Implemented ElasticSearch rollover strategy to optimize
the monthly indices rotation (events, sessions)</li>
+ <li>Implemented ElasticSearch rollover strategy to optimize
the monthly indices rotation (events,
+ sessions)
+ </li>
<li>Bug fixes and improvements in the profile merge system</li>
<li>New JSON Schema endpoint allowing for direct validation of
events</li>
<li>Performance improvements for direct profile export to
CSV</li>
@@ -221,293 +283,329 @@
<hr class="featurette-divider">
<div class="row">
- <div class="col-lg-6 pl-5">
+ <div class="col-lg-6 pl-5">
<h3>Version 2.0 released !</h3>
<h4>JSON Schema</h4>
<ul>
- <li>Define strict structure for events</li>
- <li>Easily extensible through plugins & API</li>
+ <li>Define strict structure for events</li>
+ <li>Easily extensible through plugins & API</li>
</ul>
<h4>GraphQL API (beta)</h4>
<ul>
- <li>Brand new GraphQL API to input events and manage all
objects</li>
- <li>Based on the OASIS CXS CDP Specification</li>
- <li>Deactivated by default for security</li>
+ <li>Brand new GraphQL API to input events and manage all
objects</li>
+ <li>Based on the OASIS CXS CDP Specification</li>
+ <li>Deactivated by default for security</li>
</ul>
<h4>Profile aliases</h4>
<ul>
- <li>Profiles may now have alias IDs, multiple IDs for a single
profile</li>
- <li>Simplifies merging of profiles</li>
- <li>Enables new use cases for integrating with external systems
(CRM IDs, ...)</li>
+ <li>Profiles may now have alias IDs, multiple IDs for a single
profile</li>
+ <li>Simplifies merging of profiles</li>
+ <li>Enables new use cases for integrating with external
systems (CRM IDs, ...)</li>
</ul>
<h4>New web tracker</h4>
<ul>
- <li>Replaces old web tracker that had dependencies on third
party library with self-sufficient code</li>
- <li>Designed to be used directly as well as extended</li>
- <li>New tutorial that illustrates its use</li>
+ <li>Replaces old web tracker that had dependencies on third
party library with self-sufficient code</li>
+ <li>Designed to be used directly as well as extended</li>
+ <li>New tutorial that illustrates its use</li>
</ul>
<h4>Lots of smaller fixes/improvements</h4>
<ul>
- <li>Migration tools from 1.6 to 2.0</li>
- <li>Docker images now use JDK 11 by default</li>
- <li>Lots more details <a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12343140";>here</a></li>
- </ul>
- </div><!-- /.col-lg-8 -->
- <div class="col-lg-6 my-auto mx-auto">
- <img src="https://json-schema.org/assets/logo.svg";
class="img-thumbnail" alt="JSON Schema Logo" />
- </div><!-- /.col-lg-4 -->
- </div><!-- /.row -->
+ <li>Migration tools from 1.6 to 2.0</li>
+ <li>Docker images now use JDK 11 by default</li>
+ <li>Lots more details <a
+
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12343140";>here</a>
+ </li>
+ </ul>
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-6 my-auto mx-auto">
+ <img src="https://json-schema.org/assets/logo.svg";
class="img-thumbnail" alt="JSON Schema Logo"/>
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
- <hr class="featurette-divider">
+ <hr class="featurette-divider">
- <div class="row">
- <div class="col-lg-6 pl-5">
+ <div class="row">
+ <div class="col-lg-6 pl-5">
<h3>Version 1.6.1 released !</h3>
<h4>Minor release with the following changes</h4>
<ul>
- <li>Bug fixes</li>
- <li>Migration fix</li>
- <li>More details <a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12351508";>here</a></li>
+ <li>Bug fixes</li>
+ <li>Migration fix</li>
+ <li>More details <a
+
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12351508";>here</a>
+ </li>
</ul>
- </div><!-- /.col-lg-8 -->
- <div class="col-lg-6 my-auto mx-auto">
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-6 my-auto mx-auto">
- </div><!-- /.col-lg-4 -->
- </div><!-- /.row -->
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
- <hr class="featurette-divider">
+ <hr class="featurette-divider">
- <div class="row">
- <div class="col-lg-6 pl-5">
+ <div class="row">
+ <div class="col-lg-6 pl-5">
<h3>Version 1.6 released !</h3>
<h4>Groovy actions REST API</h4>
<ul>
- <li>Deploy Groovy actions directly through API</li>
- <li>Makes it possible to use Groovy actions in cloud
deployments!</li>
+ <li>Deploy Groovy actions directly through API</li>
+ <li>Makes it possible to use Groovy actions in cloud
deployments!</li>
</ul>
<h4>Rule engine optimization</h4>
<ul>
- <li>Rule are now associated to event types in memory</li>
- <li>Only rules related to incoming event are evaluated</li>
- <li>Changes rule engine performance from exponential to linear
when rules are added</li>
+ <li>Rule are now associated to event types in memory</li>
+ <li>Only rules related to incoming event are evaluated</li>
+ <li>Changes rule engine performance from exponential to linear
when rules are added</li>
</ul>
<h4>Lots of smaller fixes/improvements</h4>
<ul>
- <li>Log4j upgrades</li>
- <li>Docker support improvements</li>
- <li>Segment and score process fixes</li>
- <li>Lots more details <a
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12350121";>here</a></li>
- </ul>
- </div><!-- /.col-lg-8 -->
- <div class="col-lg-6 my-auto mx-auto">
- <img src="assets/images/groovy-logo.svg" class="img-thumbnail"
alt="Apache Groovy logo" />
- </div><!-- /.col-lg-4 -->
- </div><!-- /.row -->
-
- <hr class="featurette-divider">
-
- <div class="row featurette">
- <div class="col-lg-4 my-auto mx-auto">
- <img src="/assets/images/unomi-meetup-logo.png"
class="img-thumbnail" alt="Unomi Meetup Logo" />
+ <li>Log4j upgrades</li>
+ <li>Docker support improvements</li>
+ <li>Segment and score process fixes</li>
+ <li>Lots more details <a
+
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12350121";>here</a>
+ </li>
+ </ul>
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-6 my-auto mx-auto">
+ <img src="assets/images/groovy-logo.svg" class="img-thumbnail"
alt="Apache Groovy logo"/>
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
+
+ <hr class="featurette-divider">
+
+ <div class="row featurette">
+ <div class="col-lg-4 my-auto mx-auto">
+ <img src="/assets/images/unomi-meetup-logo.png"
class="img-thumbnail" alt="Unomi Meetup Logo"/>
<p>Find more details on the <a
href="/community/events/meetups/2021-11-18.html">event's page</a>.</p>
- </div><!-- /.col-lg-4 -->
- <div class="col-lg-8 pl-5">
+ </div><!-- /.col-lg-4 -->
+ <div class="col-lg-8 pl-5">
<h3>First Apache Unomi meetup !</h3>
<p>
- The event was held on <strong>Nov 18th, 2021 from 1600 to 1800
CET</strong>. See the event's page for
- information about viewing the recorded session.
+ The event was held on <strong>Nov 18th, 2021 from 1600 to 1800
CET</strong>. See the event's page for
+ information about viewing the recorded session.
</p>
- </div><!-- /.col-lg-8 -->
- </div><!-- /.row -->
+ </div><!-- /.col-lg-8 -->
+ </div><!-- /.row -->
- <hr class="featurette-divider">
+ <hr class="featurette-divider">
- <div class="row">
- <div class="col-lg-6 pl-5">
+ <div class="row">
+ <div class="col-lg-6 pl-5">
<h3>Version 1.5 released !</h3>
<h4>ElasticSearch 7 support</h4>
<ul>
- <li>New data model to support ElasticSearch 7 and up</li>
- <li>Better compatibility with Kibana</li>
- <li>Migration tool updated to make the upgrade from the old to
the new data model seamless</li>
+ <li>New data model to support ElasticSearch 7 and up</li>
+ <li>Better compatibility with Kibana</li>
+ <li>Migration tool updated to make the upgrade from the old to
the new data model seamless</li>
</ul>
<h4>Docker / Cloud improvements</h4>
<ul>
- <li>Official Docker image now on Docker Hub!</li>
- <li>Improved Docker project to be in line with latest project
builds</li>
+ <li>Official Docker image now on Docker Hub!</li>
+ <li>Improved Docker project to be in line with latest project
builds</li>
</ul>
<h4>Profiles</h4>
<ul>
- <li>Added last updated property to profiles to make it easy to
query last modified profiles</li>
+ <li>Added last updated property to profiles to make it easy to
query last modified profiles</li>
</ul>
<h4>Actions</h4>
<ul>
- <li>It is now possible to build Unomi actions using Groovy
scripts inside a plugin</li>
+ <li>It is now possible to build Unomi actions using Groovy
scripts inside a plugin</li>
</ul>
<h4>JDK support</h4>
<ul>
- <li>Both JDK 11 and JDK 8 are now supported.</li>
+ <li>Both JDK 11 and JDK 8 are now supported.</li>
</ul>
<h4>Kafka support</h4>
<ul>
- <li>Initial Kafka consumer support</li>
+ <li>Initial Kafka consumer support</li>
</ul>
</p>
- </div><!-- /.col-lg-8 -->
- <div class="col-lg-6 my-auto mx-auto">
- <img src="assets/images/apache-unomi-functionalities.png"
class="img-thumbnail" alt="Apache Unomi profile view shell command" />
- </div><!-- /.col-lg-4 -->
- </div><!-- /.row -->
-
- <hr class="featurette-divider">
-
- <div class="row">
- <div class="col-lg-4 my-auto mx-auto">
- <img src="assets/images/unomi-profile-view.png"
class="img-thumbnail" alt="Apache Unomi profile view shell command" width="350"
/>
- </div><!-- /.col-lg-4 -->
- <div class="col-lg-8 pl-5">
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-6 my-auto mx-auto">
+ <img src="assets/images/apache-unomi-functionalities.png"
class="img-thumbnail"
+ alt="Apache Unomi profile view shell command"/>
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
+
+ <hr class="featurette-divider">
+
+ <div class="row">
+ <div class="col-lg-4 my-auto mx-auto">
+ <img src="assets/images/unomi-profile-view.png"
class="img-thumbnail"
+ alt="Apache Unomi profile view shell command" width="350"/>
+ </div><!-- /.col-lg-4 -->
+ <div class="col-lg-8 pl-5">
<h3>Version 1.4.0 released !</h3>
<h4>Container/Cloud deployments</h4>
<ul>
- <li>Centralized configuration compatible with Docker environment
variables
- </li>
- <li>New Dockerfile and Docker Compose project files (official
Apache Unomi Docker image coming soon!)
- </li>
+ <li>Centralized configuration compatible with Docker
environment variables
+ </li>
+ <li>New Dockerfile and Docker Compose project files (official
Apache Unomi Docker image coming soon!)
+ </li>
</ul>
<h4>Event, rules, profiles management and tools</h4>
<ul>
- <li>New Karaf Shell Commands to view events, sessions and
profiles, analyze rule executions, view incoming events, and much more...</li>
- <li>Endpoint to search in events has been added</li>
- <li>New patch system to improve modifying default definitions
(rules, segments, â¦)</li>
+ <li>New Karaf Shell Commands to view events, sessions and
profiles, analyze rule executions, view
+ incoming events, and much more...
+ </li>
+ <li>Endpoint to search in events has been added</li>
+ <li>New patch system to improve modifying default definitions
(rules, segments, â¦)</li>
</ul>
<h4>Data collection</h4>
<ul>
- <li>Analytics.js integration, providing an out-of-the-box
ready-to-use web tracker</li>
+ <li>Analytics.js integration, providing an out-of-the-box
ready-to-use web tracker</li>
</ul>
</p>
- </div><!-- /.col-lg-8 -->
- </div><!-- /.row -->
+ </div><!-- /.col-lg-8 -->
+ </div><!-- /.row -->
- <hr class="featurette-divider">
+ <hr class="featurette-divider">
- <div class="row featurette">
- <div class="col-lg-8 pl-5">
+ <div class="row featurette">
+ <div class="col-lg-8 pl-5">
<h3>Version 1.3.0 introduced Privacy (GPDR consent management)
features</h3>
<p>New in release 1.3.0 are features to manage visitor consents,
- in order to make it easier to comply with new privacy
regulations such as the <a target="_blank"
-
href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation";>GDPR</a>.
- A quick guide to these new features is also available <a
href="manual/latest/#_consent_api">here</a>.</p>
- </div><!-- /.col-lg-8 -->
- <div class="col-lg-4 my-auto mx-auto">
- <img src="assets/images/europe-gdpr.jpg" class="img-thumbnail"
alt="GDPR Illustration" width="350" />
- </div><!-- /.col-lg-4 -->
- </div><!-- /.row -->
-
- <hr class="featurette-divider">
-
- <div class="row featurette">
- <div class="col-md-12">
- <h2 class="featurette-heading">Why would you need a <span
class="text-muted">Customer Data Platform</span> ?</h2>
- <p>Organizations collect data from multiple sources and channels -
sales, web, emails, mobile, brick and mortar - and all of this data is spread
across different departments and technologies. As a result, many professionals
are lacking the data they need to do their job, especially data analysts and
marketers.</p>
- <p>A customer data platform helps business users collect all the
customer data in one place, providing a complete view of the customers. When
the data is collected, the customer data platform will also play a key role in
choosing which content or offer is more relevant to a customer.</p>
- </div>
+ in order to make it easier to comply with new privacy
regulations such as the <a target="_blank"
+
href="https://en.wikipedia.org/wiki/General_Data_Protection_Regulation";>GDPR</a>.
+ A quick guide to these new features is also available <a
href="manual/latest/#_consent_api">here</a>.
+ </p>
+ </div><!-- /.col-lg-8 -->
+ <div class="col-lg-4 my-auto mx-auto">
+ <img src="assets/images/europe-gdpr.jpg" class="img-thumbnail"
alt="GDPR Illustration" width="350"/>
+ </div><!-- /.col-lg-4 -->
+ </div><!-- /.row -->
+
+ <hr class="featurette-divider">
+
+ <div class="row featurette">
+ <div class="col-md-12">
+ <h2 class="featurette-heading">Why would you need a <span
class="text-muted">Customer Data Platform</span> ?
+ </h2>
+ <p>Organizations collect data from multiple sources and channels -
sales, web, emails, mobile, brick and
+ mortar - and all of this data is spread across different
departments and technologies. As a result, many
+ professionals are lacking the data they need to do their job,
especially data analysts and
+ marketers.</p>
+ <p>A customer data platform helps business users collect all the
customer data in one place, providing a
+ complete view of the customers. When the data is collected,
the customer data platform will also play a
+ key role in choosing which content or offer is more relevant
to a customer.</p>
</div>
+ </div>
- <div class="row featurette pt-5">
- <div class="col-md-12">
+ <div class="row featurette pt-5">
+ <div class="col-md-12">
<h2 class="featurette-heading">The <span class="text-muted">Apache
Unomi™</span> advantage ?</h2>
- <p>Each organization is unique and will always have specific
needs, this is why Apache Unomi™ has been designed to be extended and to
ease the integration of external data. The embedded features such as
segmentation, scoring and built-in privacy will be appreciated by business
users while horizontal scalability and open source positioning will be loved by
developers and architects. </p>
- <p>Apache Unomi™ is also the reference implementation of the
upcoming OASIS Context Server Customer Data Platform (CDP) standard (<a
target="_blank"
href="https://www.oasis-open.org/committees/cxs/";>https://www.oasis-open.org/committees/cxs/</a>)
to help standardize personalization of customer experience while promoting
ethical web experience management and increased user privacy controls. </p>
- </div>
+ <p>Each organization is unique and will always have specific
needs, this is why Apache Unomi™ has been
+ designed to be extended and to ease the integration of
external data. The embedded features such as
+ segmentation, scoring and built-in privacy will be appreciated
by business users while horizontal
+ scalability and open source positioning will be loved by
developers and architects. </p>
+ <p>Apache Unomi™ is also the reference implementation of the
upcoming OASIS Context Server Customer
+ Data Platform (CDP) standard (<a target="_blank"
href="https://www.oasis-open.org/committees/cxs/";>https://www.oasis-open.org/committees/cxs/</a>)
+ to help standardize personalization of customer experience
while promoting ethical web experience
+ management and increased user privacy controls. </p>
</div>
+ </div>
- <div class="row featurette pt-5">
- <div class="col-md-12">
- <h2 class="featurette-heading">Business cases based on <span
class="text-muted">Apache Unomi™</span> ?</h2>
- <ul>
- <li>Build a web personalization software to adapt the content on
your website to your audience</li>
- <li>Collect data from mobile application and feed Apache
Unomi™ to track and understand your customersâ journeys</li>
- <li>Connect the beacons deployed in your stores to Apache
Unomi™ and consolidate the profile of your customers and leads across all
these channels</li>
- <li>Automatically push profiles from Apache Unomi™ to your
CRM when a lead reach a given number of points in one of your scoring plans</li>
+ <div class="row featurette pt-5">
+ <div class="col-md-12">
+ <h2 class="featurette-heading">Business cases based on <span
class="text-muted">Apache Unomi™</span> ?
+ </h2>
+ <ul>
+ <li>Build a web personalization software to adapt the content
on your website to your audience</li>
+ <li>Collect data from mobile application and feed Apache
Unomi™ to track and understand your
+ customersâ journeys
+ </li>
+ <li>Connect the beacons deployed in your stores to Apache
Unomi™ and consolidate the profile of
+ your customers and leads across all these channels
+ </li>
+ <li>Automatically push profiles from Apache Unomi™ to
your CRM when a lead reach a given number of
+ points in one of your scoring plans
+ </li>
</ul>
- </div>
</div>
+ </div>
- <div class="row featurette pt-5">
- <div class="col-md-12">
+ <div class="row featurette pt-5">
+ <div class="col-md-12">
<h2 class="featurette-heading"><span class="text-muted">Apache
Unomi™</span> logical architecture</h2>
<p>All communication is done using HTTP REST requests and JSON
data formats.</p>
- </div>
</div>
+ </div>
- <div class="row featurette">
- <div class="col-md-12">
- <img src="assets/images/unomi-logical-architecture-diagram.png"
alt="Apache Unomi logical architecture diagram" class="img-fluid" />
- </div>
+ <div class="row featurette">
+ <div class="col-md-12">
+ <img src="assets/images/unomi-logical-architecture-diagram.png"
+ alt="Apache Unomi logical architecture diagram"
class="img-fluid"/>
</div>
+ </div>
- <div class="row featurette pt-5">
- <div class="col-md-6">
+ <div class="row featurette pt-5">
+ <div class="col-md-6">
<h2>For developers</h2>
<ul>
- <li>Uses ElasticSearch for data storage, dynamic data
structure</li>
- <li>Highly scalable architecture</li>
- <li>Very simple to deploy and install (simply unzip &
run)</li>
- <li>Uses Apache Karaf™ as the OSGi runtime</li>
- <li>Full & simple REST API</li>
- <li>Extensible through plugin architecture (using OSGi &
simple JSON descriptors)</li>
- <li>Apache Open Source project</li>
+ <li>Uses ElasticSearch for data storage, dynamic data
structure</li>
+ <li>Highly scalable architecture</li>
+ <li>Very simple to deploy and install (simply unzip &
run)</li>
+ <li>Uses Apache Karaf™ as the OSGi runtime</li>
+ <li>Full & simple REST API</li>
+ <li>Extensible through plugin architecture (using OSGi &
simple JSON descriptors)</li>
+ <li>Apache Open Source project</li>
</ul>
- </div>
- <div class="col-md-6">
+ </div>
+ <div class="col-md-6">
<h2>For IT stakeholders and business users</h2>
<ul>
- <li>First-Party Data Collection and Ownership</li>
- <li>Persistent and consolidated profiles for all your audience
(customers & leads), storing anonymous and personally identifiable
information</li>
- <li>Regulation-proof and privacy management built-in</li>
- <li>Real-Time Decisioning (Scoring logics, segmentation)</li>
- <li>Open standard, easy integration and extension</li>
+ <li>First-Party Data Collection and Ownership</li>
+ <li>Persistent and consolidated profiles for all your audience
(customers & leads), storing
+ anonymous and personally identifiable information
+ </li>
+ <li>Regulation-proof and privacy management built-in</li>
+ <li>Real-Time Decisioning (Scoring logics, segmentation)</li>
+ <li>Open standard, easy integration and extension</li>
</ul>
- </div>
</div>
+ </div>
- <div class="row featurette pt-5">
- <div class="col-md-12">
+ <div class="row featurette pt-5">
+ <div class="col-md-12">
<h2 class="featurette-heading">Articles & slides</h2>
<p>Checkout the latest <a
href="resources.html#articlesAndSlides">articles and slides</a></p>
- </div>
</div>
+ </div>
- <div class="row featurette mb-5 pt-5">
- <div class="col-md-7">
+ <div class="row featurette mb-5 pt-5">
+ <div class="col-md-7">
<h2 class="featurette-heading">Apache & OpenSource.</h2>
<p>
- Unomi™ is your project ! Unomi™ is an Apache
Software Foundation project, available under the Apache v2 license.
- It's a complete open community, always listening proposals and
comments.
- Sources, mailing lists, issue tracker: it's fully open, you can
access directly.
- We also love contributions : don't hesitate to contribute.
+ Unomi™ is your project ! Unomi™ is an Apache
Software Foundation project, available under
+ the Apache v2 license.
+ It's a complete open community, always listening proposals and
comments.
+ Sources, mailing lists, issue tracker: it's fully open, you
can access directly.
+ We also love contributions : don't hesitate to contribute.
</p>
<p>
- <a href="community/index.html">Be Involved In The Community</a> |
- <a href="contribute/index.html">How To Contribute</a>
+ <a href="community/index.html">Be Involved In The
Community</a> |
+ <a href="contribute/index.html">How To Contribute</a>
</p>
- </div>
- <div class="col-md-5 align-items-center">
+ </div>
+ <div class="col-md-5 align-items-center">
<a href="http://apache.org"; target="_blank">
- <img class="featurette-image img-fluid mx-auto"
src="assets/images/apache.png" alt="Apache Software Foundation">
+ <img class="featurette-image img-fluid mx-auto"
src="assets/images/apache.png"
+ alt="Apache Software Foundation">
</a>
<br><br><br>
<a href="https://events.apache.org/x/current-event.html";
target="_blank">
- <img class="featurette-image img-fluid mx-auto"
src="http://www.apache.org/events/current-event-234x60.png"; alt="ApacheCon" />
+ <img class="featurette-image img-fluid mx-auto"
+
src="http://www.apache.org/events/current-event-234x60.png"; alt="ApacheCon"/>
</a>
- </div>
</div>
+ </div>
- <!-- /END THE FEATURETTES -->
+ <!-- /END THE FEATURETTES -->
- </div><!-- /.container -->
+</div><!-- /.container -->
</main>
![https://json-schema.org/assets/logo.svg"](https://json-schema.org/assets/logo.svg"){kind=link}
![http://www.apache.org/events/current-event-234x60.png"](http://www.apache.org/events/current-event-234x60.png"){kind=link}