Author: jkevan
Date: Tue Apr 4 13:18:11 2023
New Revision: 1908955
URL: http://svn.apache.org/viewvc?rev=1908955&view=rev
Log:
[scm-publish] Updating Unomi website
Modified:
unomi/website/community/maturity-model-report.html
unomi/website/community/policies.html
unomi/website/community/team.html
unomi/website/connectors.html
unomi/website/contribute/become-a-committer.html
unomi/website/contribute/dependencies-guide.html
unomi/website/contribute/manual-release-guide.html
unomi/website/contribute/post-commit-policies-details.html
unomi/website/contribute/release-guide.html
unomi/website/documentation.html
unomi/website/download.html
unomi/website/get-started.html
unomi/website/index.html
unomi/website/resources.html
unomi/website/use-cases.html
Modified: unomi/website/community/maturity-model-report.html
URL:
http://svn.apache.org/viewvc/unomi/website/community/maturity-model-report.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/community/maturity-model-report.html (original)
+++ unomi/website/community/maturity-model-report.html Tue Apr 4 13:18:11 2023
@@ -96,7 +96,7 @@
<h3>Overview</h3>
<p>
- This is an assessment of the Unomi podling???s maturity, meant to
help inform the decision (of the mentors, community, Incubator PMC and ASF
Board of Directors) to graduate
+ This is an assessment of the Unomi podlingâs maturity, meant to
help inform the decision (of the mentors, community, Incubator PMC and ASF
Board of Directors) to graduate
it as a top-level Apache project. It is based on the ASF project
maturity model at <a target="_blank"
href="https://community.apache.org/apache-way/apache-project-maturity-model.html";>https://community.apache.org/apache-way/apache-project-maturity-model.html</a>
Maintaining such a file is a new, experimental idea as part of the
continuous improvement of the ASF incubation process.
</p>
@@ -108,7 +108,7 @@
<h3>Overall assessment</h3>
<p>
- Just introduced this report card, we will need to evaluate all the
model???s parts to see how we fare so far.
+ Just introduced this report card, we will need to evaluate all the
modelâs parts to see how we fare so far.
</p>
<h3>Maturity model assessment</h3>
@@ -142,7 +142,7 @@
</tr>
<tr>
<td><strong>CD20</strong></td>
- <td>The project???s code is easily discoverable and publicly
accessible.</td>
+ <td>The projectâs code is easily discoverable and publicly
accessible.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>it is linked from the main project site and accessible in
the public ASF git repository</td>
</tr>
@@ -154,7 +154,7 @@
</tr>
<tr>
<td><strong>CD40</strong></td>
- <td>The full history of the project???s code is available via
a source code control system, in a way that allows any released version to be
recreated.</td>
+ <td>The full history of the projectâs code is available via
a source code control system, in a way that allows any released version to be
recreated.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>everything is in the ASF Git repository.</td>
</tr>
@@ -187,7 +187,7 @@
</tr>
<tr>
<td><strong>LC20</strong></td>
- <td>Libraries that are mandatory dependencies of the
project???s code do not create more restrictions than the Apache License
does.</td>
+ <td>Libraries that are mandatory dependencies of the
projectâs code do not create more restrictions than the Apache License
does.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>NOTICE files contain all the information and has been
reviewed on two releases already</td>
</tr>
@@ -199,7 +199,7 @@
</tr>
<tr>
<td><strong>LC40</strong></td>
- <td>Committers are bound by an Individual Contributor
Agreement (the ???Apache iCLA???) that defines which code they are allowed to
commit and how they need to identify code that is not their own.</td>
+ <td>Committers are bound by an Individual Contributor
Agreement (the âApache iCLAâ) that defines which code they are allowed to
commit and how they need to identify code that is not their own.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>All committers have registered iCLAs</td>
</tr>
@@ -232,7 +232,7 @@
</tr>
<tr>
<td><strong>RE20</strong></td>
- <td>Releases are approved by the project???s PMC (see CS10),
in order to make them an act of the Foundation.</td>
+ <td>Releases are approved by the projectâs PMC (see CS10),
in order to make them an act of the Foundation.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>Happened for three major releases already</td>
</tr>
@@ -244,7 +244,7 @@
</tr>
<tr>
<td><strong>RE40</strong></td>
- <td>Convenience binaries can be distributed alongside source
code but they are not Apache Releases ??? they are just a convenience provided
with no guarantee.</td>
+ <td>Convenience binaries can be distributed alongside source
code but they are not Apache Releases â they are just a convenience provided
with no guarantee.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>See the releases <a href="../download.html">here</a></td>
</tr>
@@ -315,7 +315,7 @@
<td><strong>CO10</strong></td>
<td>The project has a well-known homepage that points to all
the information required to operate according to this maturity model.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
- <td>See the <a class="externalLink" target="_blank"
href="http://unomi.incubator.apache.org";>project???s home page</a> that
includes a <a href="../contribute/index.html">contribute</a> section
+ <td>See the <a class="externalLink" target="_blank"
href="http://unomi.incubator.apache.org";>projectâs home page</a> that
includes a <a href="../contribute/index.html">contribute</a> section
that describes how to become a committer as well as <a
href="../contribute/become-a-committer.html">several</a> <a
href="../contribute/committer-guide.html">documents</a> for on-board newcomers
quickly</td>
</tr>
<tr>
@@ -374,13 +374,13 @@
<tbody>
<tr>
<td><strong>CS10</strong></td>
- <td>The project maintains a public list of its contributors
who have decision power ??? the project???s PMC (Project Management Committee)
consists of those contributors.</td>
+ <td>The project maintains a public list of its contributors
who have decision power â the projectâs PMC (Project Management Committee)
consists of those contributors.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>The project has a <a href="team.html">team page</a> that
lists all the contributors along with their associated roles.</td>
</tr>
<tr>
<td><strong>CS20</strong></td>
- <td>Decisions are made by consensus among PMC members and are
documented on the project???s main communications channel. Community opinions
are taken into account but the PMC has the final word if needed.</td>
+ <td>Decisions are made by consensus among PMC members and are
documented on the projectâs main communications channel. Community opinions
are taken into account but the PMC has the final word if needed.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>PPMC decisions have been unonimous so far, including
voting new committers and new PPMC members. The project has been making
important decisions on the project mailing lists. All community decisions have
had a consensus without any PPMC action needed.</td>
</tr>
@@ -394,11 +394,11 @@
<td><strong>CS40</strong></td>
<td>In Apache projects, vetoes are only valid for code commits
and are justified by a technical explanation, as per the Apache voting rules
defined in CS30.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
- <td>The project hasn???t used a veto at any point and relies
on robust code reviews, especially for any issues around licenses problems.</td>
+ <td>The project hasnât used a veto at any point and relies
on robust code reviews, especially for any issues around licenses problems.</td>
</tr>
<tr>
<td><strong>CS50</strong></td>
- <td>All ???important??? discussions happen asynchronously in
written form on the project???s main communications channel. Offline,
face-to-face or private discussions that affect the project are also documented
on that channel.</td>
+ <td>All âimportantâ discussions happen asynchronously in
written form on the projectâs main communications channel. Offline,
face-to-face or private discussions that affect the project are also documented
on that channel.</td>
<td class="text-center"><i class="fas fa-check
text-success"></i></td>
<td>The project has been making important decisions on the
project mailing lists. When communication occurs on side channels (Slack,
face-to-face mostly), the mailing list is always used to communicate important
information to the community.</td>
</tr>
Modified: unomi/website/community/policies.html
URL:
http://svn.apache.org/viewvc/unomi/website/community/policies.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/community/policies.html (original)
+++ unomi/website/community/policies.html Tue Apr 4 13:18:11 2023
@@ -100,7 +100,7 @@
<p>Apache Unomi makes minor releases every 6 weeks. Apache Unomi has
a <a target="_blank"
href="https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com";>calendar</a>
for cutting the next release branch. After a release branch is cut, the
community works quickly to finalize that release.</p>
- <p>Apache Unomi aims to make 8 releases in a 12 month period. To
accommodate users with longer upgrade cycles, some of these releases will be
tagged as long term support (LTS) releases. LTS releases receive patches to fix
major issues for 12 months, starting from the release?????™s initial
release date. There will be at least one new LTS release in a 12 month period,
and LTS releases are considered deprecated after 12 months. The community will
mark a release as a LTS release based on various factors, such as the number of
LTS releases currently in flight and whether the accumulated feature set since
the last LTS provides significant upgrade value. Non-LTS releases do not
receive patches and are considered deprecated immediately after the next
following minor release. We encourage you to update early and often; do not
wait until the deprecation date of the version you are using.</p>
+ <p>Apache Unomi aims to make 8 releases in a 12 month period. To
accommodate users with longer upgrade cycles, some of these releases will be
tagged as long term support (LTS) releases. LTS releases receive patches to fix
major issues for 12 months, starting from the releaseâ⬙s initial
release date. There will be at least one new LTS release in a 12 month period,
and LTS releases are considered deprecated after 12 months. The community will
mark a release as a LTS release based on various factors, such as the number of
LTS releases currently in flight and whether the accumulated feature set since
the last LTS provides significant upgrade value. Non-LTS releases do not
receive patches and are considered deprecated immediately after the next
following minor release. We encourage you to update early and often; do not
wait until the deprecation date of the version you are using.</p>
<p>It is up to the Apache Unomi community to decide whether an
identified issue is a major issue that warrants a patch release. Some examples
of major issues are high severity security issues and high risk data integrity
issues.</p>
Modified: unomi/website/community/team.html
URL:
http://svn.apache.org/viewvc/unomi/website/community/team.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/community/team.html (original)
+++ unomi/website/community/team.html Tue Apr 4 13:18:11 2023
@@ -281,7 +281,7 @@
<td>-</td>
<td>Régis Mora</td>
<td>-</td>
- <td>P??kin Accueil</td>
+ <td>Pékin Accueil</td>
<td><a class="externalLink" target="_blank"
href="https://www.pekin-accueil.com";>https://www.pekin-accueil.com</a></td>
<td>Retired (was initial committer, PPMC)</td>
<td>+8</td>
Modified: unomi/website/connectors.html
URL:
http://svn.apache.org/viewvc/unomi/website/connectors.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/connectors.html (original)
+++ unomi/website/connectors.html Tue Apr 4 13:18:11 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.2.0-SNAPSHOT</span></h3>
+ <h3 class="mb-0 text-dark">MailChimp <span
class="text-muted">2.3.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/become-a-committer.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/become-a-committer.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/contribute/become-a-committer.html (original)
+++ unomi/website/contribute/become-a-committer.html Tue Apr 4 13:18:11 2023
@@ -179,7 +179,7 @@
<li>They earnestly try to make Unomi better with their own
code</li>
<li>They earnestly try to make Unomi better with code
review</li>
<li>They accept and integrate feedback on their code</li>
- <li>They know, follow, and enforce Unomi?????™s
practices while reviewing/merging code - style, documentation, testing,
backward compatibility, etc.</li>
+ <li>They know, follow, and enforce Unomiâ⬙s
practices while reviewing/merging code - style, documentation, testing,
backward compatibility, etc.</li>
</ul>
</li>
</ul>
Modified: unomi/website/contribute/dependencies-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/dependencies-guide.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/contribute/dependencies-guide.html (original)
+++ unomi/website/contribute/dependencies-guide.html Tue Apr 4 13:18:11 2023
@@ -118,7 +118,7 @@
<h2>Dependencies Guide</h2>
<p>This document describes policies for keeping Unomi dependencies
up to date.</p>
- <p>Old dependencies cause user pain and can result in a system
being unusable for some users. Many users do not use Unomi in isolation and
bundle other dependencies in the same deployment. These additional dependencies
might pull in incompatible dependencies to user?????™s environment which
can again result in broken Unomi pipelines, sometimes with undefined behavior.
To prevent this, users will have to update their deployment environment or
worse yet may end up not being able to use Unomi along with some of the other
dependencies at all.</p>
+ <p>Old dependencies cause user pain and can result in a system
being unusable for some users. Many users do not use Unomi in isolation and
bundle other dependencies in the same deployment. These additional dependencies
might pull in incompatible dependencies to userâ⬙s environment which
can again result in broken Unomi pipelines, sometimes with undefined behavior.
To prevent this, users will have to update their deployment environment or
worse yet may end up not being able to use Unomi along with some of the other
dependencies at all.</p>
<p>If a component <em>X</em> chooses to override the version of a
dependency <em>D</em> from <em>a</em> to <em>b</em> and another component
<em>Y</em> is incompatible with version <em>b</em> of <em>D</em>, deployment of
a user that uses both components <em>X</em> and <em>Y</em> will end up in a
broken state.</p>
@@ -182,7 +182,7 @@
<p><strong>Dependencies of Java SDK components that may cause
issues to other components if leaked should be vendored.</strong></p>
- <p><a target="_blank"
href="https://www.ardanlabs.com/blog/2013/10/manage-dependencies-with-godep.html";>Vendoring</a>
is the process of creating copies of third party dependencies. Combined with
repackaging, vendoring will allow Unomi components to depend on third party
libraries without causing conflicts to other components. Vendoring should be
done in a case-by-case basis since this can increase the total number of
dependencies deployed in user?????™s enviroment.</p>
+ <p><a target="_blank"
href="https://www.ardanlabs.com/blog/2013/10/manage-dependencies-with-godep.html";>Vendoring</a>
is the process of creating copies of third party dependencies. Combined with
repackaging, vendoring will allow Unomi components to depend on third party
libraries without causing conflicts to other components. Vendoring should be
done in a case-by-case basis since this can increase the total number of
dependencies deployed in userâ⬙s enviroment.</p>
<h3>Dependency updates and backwards compatibility</h3>
Modified: unomi/website/contribute/manual-release-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/manual-release-guide.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/contribute/manual-release-guide.html (original)
+++ unomi/website/contribute/manual-release-guide.html Tue Apr 4 13:18:11 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.2.0.
- Ideally all tickets listed for version: 2.2.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.3.0.
+ Ideally all tickets listed for version: 2.3.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.2.0. It will be useful for
linking the release notes in the voting mail.
+ By choosing the version: 2.3.0. It will be useful for
linking the release notes in the voting mail.
</li>
</ol>
@@ -226,17 +226,17 @@ gpg --verify test.txt.asc test.txt
<ol>
<li>Clone and checkout the project using:
<pre class="alert alert-primary"><code>git clone
https://gitbox.apache.org/repos/asf/unomi.git</code></pre>
- in a separate directory, to make sure you don???t have any
additional files in the build
+ in a separate directory, to make sure you donât have any
additional files in the build
(such as allCountries.zip or other binary files that should
not be there)</li>
<li>
Simply checkout an existing branch for release
<pre class="alert alert-primary"><code>cd unomi
-git checkout unomi-2.1.x
+git checkout unomi-2.2.x
</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.1.x
+git checkout -b unomi-2.2.x
</code></pre>
</li>
</ol>
@@ -253,9 +253,9 @@ git checkout -b unomi-2.1.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.2.0-SNAPSHOT.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-2.3.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
+ <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)
</li>
<li>Check the Copyright notice years in the NOTICE file and
anywhere else where it might be (by using search and replace)</li>
@@ -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.2.0-SNAPSHOT-source-release.zip.asc
unomi-root-2.2.0-SNAPSHOT-source-release.zip
-shasum -a 512 unomi-root-2.2.0-SNAPSHOT-source-release.zip
-cat unomi-root-2.2.0-SNAPSHOT-source-release.zip.sha512
-unzip unomi-root-2.2.0-SNAPSHOT-source-release.zip
-cd unomi-root-2.2.0-SNAPSHOT
+gpg --verify unomi-root-2.3.0-SNAPSHOT-source-release.zip.asc
unomi-root-2.3.0-SNAPSHOT-source-release.zip
+shasum -a 512 unomi-root-2.3.0-SNAPSHOT-source-release.zip
+cat unomi-root-2.3.0-SNAPSHOT-source-release.zip.sha512
+unzip unomi-root-2.3.0-SNAPSHOT-source-release.zip
+cd unomi-root-2.3.0-SNAPSHOT
mvn clean install
popd</code></pre>
to check that the packaged source build properly
@@ -304,14 +304,14 @@ popd</code></pre>
<pre class="alert alert-primary"><code>mvn -DskipITs=true
-DskipTests=true -Drelease.arguments="-Papache-release,integration-tests
-DskipITs=true -DskipTests=true" -P integration-tests,docker,\!run-tests
release:perform</code></pre>
</li>
<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:
+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.2.0
+scm.tag=unomi-root-2.3.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.2.0 Release Candidate 1</strong>
+ <strong>Apache Unomi 2.3.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.2.0</code></pre>
+mkdir 2.3.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.2.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.2.0/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.3.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.3.0/</a>
and
- <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.2.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.2.0/</a>
+ <a
href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.3.0/";
target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.3.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.2.0/unomi-root-2.2.0-source-release.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.2.0/unomi-root-2.2.0-source-release.zip.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.2.0/unomi-2.2.0.tar.gz
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.2.0/unomi-2.2.0.tar.gz.asc
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.2.0/unomi-2.2.0.zip
-wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.2.0/unomi-2.2.0.zip.asc</code></pre>
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.3.0/unomi-2.3.0.tar.gz
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.3.0/unomi-2.3.0.tar.gz.asc
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.3.0/unomi-2.3.0.zip
+wget
https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.3.0/unomi-2.3.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.2.0-source-release.zip unomi-2.2.0-src.zip
-mv unomi-root-2.2.0-source-release.zip.asc unomi-2.2.0-src.zip.asc
-shasum -a 512 unomi-2.2.0-src.zip > unomi-2.2.0-src.zip.sha512
-
-mv unomi-2.2.0.zip unomi-2.2.0-bin.zip
-mv unomi-2.2.0.zip.asc unomi-2.2.0-bin.zip.asc
-shasum -a 512 unomi-2.2.0-bin.zip > unomi-2.2.0-bin.zip.sha512
-
-mv unomi-2.2.0.tar.gz unomi-2.2.0-bin.tar.gz
-mv unomi-2.2.0.tar.gz.asc unomi-2.2.0-bin.tar.gz.asc
-shasum -a 512 unomi-2.2.0-bin.tar.gz > unomi-2.2.0-bin.tar.gz.sha512
+mv unomi-root-2.3.0-source-release.zip unomi-2.3.0-src.zip
+mv unomi-root-2.3.0-source-release.zip.asc unomi-2.3.0-src.zip.asc
+shasum -a 512 unomi-2.3.0-src.zip > unomi-2.3.0-src.zip.sha512
+
+mv unomi-2.3.0.zip unomi-2.3.0-bin.zip
+mv unomi-2.3.0.zip.asc unomi-2.3.0-bin.zip.asc
+shasum -a 512 unomi-2.3.0-bin.zip > unomi-2.3.0-bin.zip.sha512
+
+mv unomi-2.3.0.tar.gz unomi-2.3.0-bin.tar.gz
+mv unomi-2.3.0.tar.gz.asc unomi-2.3.0-bin.tar.gz.asc
+shasum -a 512 unomi-2.3.0-bin.tar.gz > unomi-2.3.0-bin.tar.gz.sha512
</code></pre>
</li>
<li>
<pre class="alert alert-primary"><code>cd ..
-svn add 2.2.0</code></pre>
+svn add 2.3.0</code></pre>
</li>
<li>
- <pre class="alert alert-primary"><code>svn commit -m "Apache
2.2.0 Release (for PMC voting)"</code></pre>
+ <pre class="alert alert-primary"><code>svn commit -m "Apache
2.3.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.2.0
-git tag -d unomi-root-2.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-2.3.0
+git tag -d unomi-root-2.3.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.2.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.2.0
https://dist.apache.org/repos/dist/release/unomi/2.2.0 -m "Apache Unomi 2.2.0
Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/2.3.0
https://dist.apache.org/repos/dist/release/unomi/2.3.0 -m "Apache Unomi 2.3.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.2.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.2.0 Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.3.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.2.0
-mv unomi-manual-2_1_x.pdf 2.2.0
-mv unomi-manual-2_1_x.pdf.asc 2.2.0
-mv unomi-manual-2_1_x.zip 2.2.0
-mv unomi-manual-2_1_x.pdf.sha512 2.2.0
-mv unomi-manual-2_1_x.zip.asc 2.2.0
-mv unomi-manual-2_1_x.zip.sha512 2.2.0
-cd 2.2.0
+svn co https://dist.apache.org/repos/dist/release/unomi/2.3.0
+mv unomi-manual-2_2_x.pdf 2.3.0
+mv unomi-manual-2_2_x.pdf.asc 2.3.0
+mv unomi-manual-2_2_x.zip 2.3.0
+mv unomi-manual-2_2_x.pdf.sha512 2.3.0
+mv unomi-manual-2_2_x.zip.asc 2.3.0
+mv unomi-manual-2_2_x.zip.sha512 2.3.0
+cd 2.3.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.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.3.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.2.0
-git tag --delete unomi-root-2.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-2.3.0
+git tag --delete unomi-root-2.3.0</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -540,7 +540,7 @@ git push origin -f</code></pre>
<h2 id="improve-the-process">Improve the process</h2>
- <p>It is important that we improve the release processes over
time. Once you???ve finished the release, please take a step back and look what
areas of this process and be improved. Perhaps some part of the process can be
simplified. Perhaps parts of this guide can be clarified.</p>
+ <p>It is important that we improve the release processes over
time. Once youâve finished the release, please take a step back and look what
areas of this process and be improved. Perhaps some part of the process can be
simplified. Perhaps parts of this guide can be clarified.</p>
<p>If we have specific ideas, please start a discussion on the
dev@ mailing list and/or propose a pull request to update this guide.
Thanks!</p>
@@ -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.2.0 release [TAKE2]
+Subject: [VOTE] Apache Unomi 2.3.0 release [TAKE2]
Body:
Hi all,
-I submit Apache Unomi 2.2.0 release [TAKE2] to your vote.
+I submit Apache Unomi 2.3.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.2.0/unomi-root-2.2.0-source-release.zip
+unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.2.0/unomi-root-2.2.0-source-release.zip>*
+unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.2.0/
+unomi/unomi/2.3.0/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.2.0/>*
+unomi/unomi/2.3.0/>*
Git tag:
-unomi-root-2.2.0
+unomi-root-2.3.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.2.0 release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi 2.3.0 release [TAKE2]
Body:
Hi,
@@ -621,7 +621,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi 2.2.0 is approved by the team.
+The proposal to release Unomi 2.3.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.2.0 Release
+Subject : [ANNOUNCE] Apache Unomi 2.3.0 Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi 2.2.0.
+Unomi 2.3.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.2.0/
+https://dist.apache.org/repos/dist/release/incubator/unomi/2.3.0/
All JIRAs completed for this release are tagged with 'FixVersion =
-2.2.0'; the JIRA release notes can be found here:
+2.3.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/post-commit-policies-details.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/post-commit-policies-details.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/contribute/post-commit-policies-details.html (original)
+++ unomi/website/contribute/post-commit-policies-details.html Tue Apr 4
13:18:11 2023
@@ -141,7 +141,7 @@
<p>Flaky tests are considered failing tests, and fixing a flaky
test is a critical/P1 issue.</p>
<p>Flaky tests are tests that randomly succeed or fail while using
the same code version. Flaky test failures are one of the most dangerous types
of failures
- because they are easy to ignore ???????? another run of the flaky
test might pass successfully. However, these failures can hide real bugs and
flaky tests often
+ because they are easy to ignore ââ¬â another run of the flaky
test might pass successfully. However, these failures can hide real bugs and
flaky tests often
slowly accumulate. Someone must repeatedly triage the failures,
and flaky tests are often the hardest ones to fix.</p>
<p>Flaky tests do not provide a reliable quality signal, so it is
important to quickly fix the flakiness. If a fix will take awhile to implement,
it is safer
Modified: unomi/website/contribute/release-guide.html
URL:
http://svn.apache.org/viewvc/unomi/website/contribute/release-guide.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/contribute/release-guide.html (original)
+++ unomi/website/contribute/release-guide.html Tue Apr 4 13:18:11 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.2.0.
- Ideally all tickets listed for version: 2.2.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.3.0.
+ Ideally all tickets listed for version: 2.3.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.2.0. It will be useful for
linking the release notes in the voting mail.
+ By choosing the version: 2.3.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.2.0 BRANCH_NAME</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-1.sh
2.3.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 !)
</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.2.0-SNAPSHOT.rat</code></pre>
+ <pre class="alert alert-primary"><code>less
target/unomi-root-2.3.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
+ <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)
</li>
<li>Check the Copyright notice years in the NOTICE file and
anywhere else where it might be (by using search and replace)</li>
@@ -263,21 +263,21 @@ gpg: signing failed: Inappropriate ioctl
<h3 id="publish-repository">Repository</h3>
<ol>
<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:
+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.2.0
+scm.tag=unomi-root-2.3.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.2.0 Release Candidate 1</strong>
+ <strong>Apache Unomi 2.3.0 Release Candidate 1</strong>
</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.2.0 orgapacheunomi-NEXUS-UNOMI-ID</code></pre>
+ <pre class="alert alert-primary"><code>./release-stage-2.sh
2.3.0 orgapacheunomi-NEXUS-UNOMI-ID</code></pre>
where NEXUS-UNOMI-ID is the ID generated by Nexus
</li>
<li>Send out to the Unomi mailing list a mail to start the
voting process, see <a href="#mail-1">[1]</a></li>
@@ -285,8 +285,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.2.0
-git tag -d unomi-root-2.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git push
--delete origin unomi-root-2.3.0
+git tag -d unomi-root-2.3.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:
@@ -306,7 +306,7 @@ git tag -d unomi-root-2.2.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.2.0
https://dist.apache.org/repos/dist/release/unomi/2.2.0 -m "Apache Unomi 2.2.0
Release"</code></pre>
+ <pre class="alert alert-primary"><code>svn mv
https://dist.apache.org/repos/dist/dev/unomi/2.3.0
https://dist.apache.org/repos/dist/release/unomi/2.3.0 -m "Apache Unomi 2.3.0
Release"</code></pre>
</li>
<li>
In JIRA mark the version as released and add a release date
@@ -344,7 +344,7 @@ git tag -d unomi-root-2.2.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.2.0 Release website update"
+ <pre class="alert alert-primary"><code>git commit -m "Apache
Unomi 2.3.0 Release website update"
git push</code></pre>
</li>
</ol>
@@ -353,7 +353,7 @@ git push</code></pre>
<ol>
<li>
- Launch <pre class="alert
alert-primary"><code>./generate-site.sh 2_1_x 2.2.0</code></pre> from the
project's
+ Launch <pre class="alert
alert-primary"><code>./generate-site.sh 2_2_x 2.3.0</code></pre> from the
project's
root directory.
</li>
<li>Check the generated site by opening
<code>target/staging/manual/index.html</code>
@@ -361,7 +361,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_1_x 2.2.0
APACHE_LDAP_USERNAME APACHE_LDAP_PASSWORD</code></pre>
+ <pre class="alert
alert-primary"><code>./generate-site-and-upload.sh 2_2_x 2.3.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
@@ -374,7 +374,7 @@ git push</code></pre>
<ol>
<li>
Checkout the tagged version:
- <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git checkout
tags/unomi-root-2.3.0</code></pre>
</li>
<li>
Change to the Docker directory. Make sure you have docker
running locally (start Docker Desktop for
@@ -392,8 +392,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.2.0
-git tag --delete unomi-root-2.2.0</code></pre>
+ <pre class="alert alert-primary"><code>git push --delete
origin unomi-root-2.3.0
+git tag --delete unomi-root-2.3.0</code></pre>
</li>
<li>Reset to the previous commit before the release preparation:
<pre class="alert alert-primary"><code>git reset --hard
c65f9897ec5f31d9d22ad639738c7db9d109aa77
@@ -433,7 +433,7 @@ git push origin -f</code></pre>
<h2 id="improve-the-process">Improve the process</h2>
- <p>It is important that we improve the release processes over
time. Once you???ve finished the release, please take a step back and look what
areas of this process and be improved. Perhaps some part of the process can be
simplified. Perhaps parts of this guide can be clarified.</p>
+ <p>It is important that we improve the release processes over
time. Once youâve finished the release, please take a step back and look what
areas of this process and be improved. Perhaps some part of the process can be
simplified. Perhaps parts of this guide can be clarified.</p>
<p>If we have specific ideas, please start a discussion on the
dev@ mailing list and/or propose a pull request to update this guide.
Thanks!</p>
@@ -443,11 +443,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.2.0 release [TAKE2]
+Subject: [VOTE] Apache Unomi 2.3.0 release [TAKE2]
Body:
Hi all,
-I submit Apache Unomi 2.2.0 release [TAKE2] to your vote.
+I submit Apache Unomi 2.3.0 release [TAKE2] to your vote.
The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
@@ -461,18 +461,18 @@ Staging Repository:
You can find the sources here :
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.2.0/unomi-root-2.2.0-source-release.zip
+unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi-root/2.2.0/unomi-root-2.2.0-source-release.zip>*
+unomi/unomi-root/2.3.0/unomi-root-2.3.0-source-release.zip>*
Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.2.0/
+unomi/unomi/2.3.0/
<https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
-unomi/unomi/2.2.0/>*
+unomi/unomi/2.3.0/>*
Git tag:
-unomi-root-2.2.0
+unomi-root-2.3.0
Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -494,7 +494,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.2.0 release [TAKE2]
+Subject: [RESULT][VOTE] Apache Unomi 2.3.0 release [TAKE2]
Body:
Hi,
@@ -514,7 +514,7 @@ John Doe 5
No 0 or -1.
-The proposal to release Unomi 2.2.0 is approved by the team.
+The proposal to release Unomi 2.3.0 is approved by the team.
Thanks,
John Doe 1
@@ -522,10 +522,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.2.0 Release
+Subject : [ANNOUNCE] Apache Unomi 2.3.0 Release
Body:
The Apache Unomi team would like to announce the release of Apache
-Unomi 2.2.0.
+Unomi 2.3.0.
Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&;
@@ -539,10 +539,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.2.0/
+https://dist.apache.org/repos/dist/release/incubator/unomi/2.3.0/
All JIRAs completed for this release are tagged with 'FixVersion =
-2.2.0'; the JIRA release notes can be found here:
+2.3.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=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/documentation.html (original)
+++ unomi/website/documentation.html Tue Apr 4 13:18:11 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.2.0-SNAPSHOT</span></h3>
+ <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">2.3.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=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/download.html (original)
+++ unomi/website/download.html Tue Apr 4 13:18:11 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.1.0</span></h3>
- <div class="mb-1 text-muted">November 28th, 2022</div>
+ <h3 class="mb-0 text-dark">Unomi <span
class="text-muted">2.2.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.1.0/unomi-2.1.0-bin.tar.gz";>tar.gz</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.tar.gz.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.tar.gz.sha512";>SHA512</a>]
-
- <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.1.0/unomi-2.1.0-bin.zip";>zip</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.zip.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.zip.sha512";>SHA512</a>]
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.2.0/unomi-2.2.0-bin.tar.gz";>tar.gz</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.0-bin.tar.gz.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.0-bin.tar.gz.sha512";>SHA512</a>]
-
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.2.0/unomi-2.2.0-bin.zip";>zip</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.0-bin.zip.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.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.1.0/unomi-2.1.0-src.zip";>zip</a>
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-src.zip.asc";>PGP</a>]
- [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.1.0/unomi-2.1.0-src.zip.sha512";>SHA512</a>]
+ <a target="_blank"
href="https://www.apache.org/dyn/closer.lua/unomi/2.2.0/unomi-2.2.0-src.zip";>zip</a>
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.0-src.zip.asc";>PGP</a>]
+ [<a target="_blank"
href="https://www.apache.org/dist/unomi/2.2.0/unomi-2.2.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=12352332";
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=12352514";
role="button" target="_blank">Release notes »</a>
</div>
</div>
</div>
@@ -172,7 +172,7 @@
</code>
<br>
<code>
- % gpg --verify unomi-2.1.0-bin.tar.gz.asc
unomi-2.1.0-bin.tar.gz
+ % gpg --verify unomi-2.2.0-bin.tar.gz.asc
unomi-2.2.0-bin.tar.gz
</code>
</p>
</div>
@@ -196,6 +196,33 @@
</thead>
<tbody>
<tr>
+ <td>2.1.0</td>
+ <td><a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.tar.gz";>tar.gz</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.tar.gz.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.tar.gz.sha512";>SHA512</a>]<br>
+ <a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.zip";>zip</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.zip.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-bin.zip.sha512";>SHA512</a>]
+ </td>
+ <td>
+ <a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-src.zip";>zip</a>
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-src.zip.asc";>PGP</a>]
+ [<a target="_blank"
+
href="https://archive.apache.org/dist/unomi/2.1.0/unomi-2.1.0-src.zip.sha512";>SHA512</a>]
+ </td>
+ <td><a target="_blank"
+
href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12352332";>Release
+ Notes</a></td>
+ </tr>
+ <tr>
<td>2.0.0</td>
<td><a target="_blank"
href="https://archive.apache.org/dist/unomi/2.0.0/unomi-2.0.0-bin.tar.gz";>tar.gz</a>
Modified: unomi/website/get-started.html
URL:
http://svn.apache.org/viewvc/unomi/website/get-started.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/get-started.html (original)
+++ unomi/website/get-started.html Tue Apr 4 13:18:11 2023
@@ -100,7 +100,7 @@
<h5 class="project-heading">What is unique about <span
class="text-muted">Apache Unomi</span> ?</h5>
<div class="pb-2 pt-2">
<p>One of the most unique features of this server is its privacy
management features. Using the privacy REST API, it is possible for integrators
to build user facing UIs that let them manage their profile, and control how
they are being tracked, what data has been collected and even anonymize
previously collected data or future data ! Finally there is even the
possibility for end-users to delete their profile information completely.</p>
- <p>It is becoming more and more important to address privacy
issues correctly, and it is even becoming more and more of a legal issue since
a lot of legislation is now appearing in many countries to make sure that
user???s right to privacy is respected.</p>
+ <p>It is becoming more and more important to address privacy
issues correctly, and it is even becoming more and more of a legal issue since
a lot of legislation is now appearing in many countries to make sure that
userâs right to privacy is respected.</p>
<p>Of course these possibilities have no default UI inside of
Apache Unomi so it is left up to the developers to expose them (or not).</p>
</div>
</div>
Modified: unomi/website/index.html
URL:
http://svn.apache.org/viewvc/unomi/website/index.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/index.html (original)
+++ unomi/website/index.html Tue Apr 4 13:18:11 2023
@@ -105,6 +105,26 @@
<div class="row">
<div class="col-lg-6 pl-5">
+ <h3>Version 2.2.0 released!</h3>
+ <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>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>
+ <li>Upgraded user agent library (Yauaa) to version 7.9.0</li>
+ <li>Other small bug fixes and improvements</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.8.0 released!</h3>
<h4>Changes in 1.8.0 (since 1.7.1)</h4>
<ul>
@@ -305,7 +325,7 @@
<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 patch system to improve modifying default definitions
(rules, segments, â¦)</li>
</ul>
<h4>Data collection</h4>
<ul>
@@ -353,7 +373,7 @@
<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>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>
Modified: unomi/website/resources.html
URL:
http://svn.apache.org/viewvc/unomi/website/resources.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/resources.html (original)
+++ unomi/website/resources.html Tue Apr 4 13:18:11 2023
@@ -136,7 +136,7 @@
<div class="row pb-2 pt-4">
<div class="col-md-6">
<h6 class="pb-2 pt-2">ApacheCon 2015 - The Apache
Unomi Project In-depth</h6>
- <p>Serge Huber, Jahia???s CTO, discusses the new
Apache Unomi project that was started in September 2015 and then demonstrates
how it can be used to build integrated solutions that use Internet Of Thing
devices and server-side technologies to build personalized user experiences.</p>
+ <p>Serge Huber, Jahiaâs CTO, discusses the new
Apache Unomi project that was started in September 2015 and then demonstrates
how it can be used to build integrated solutions that use Internet Of Thing
devices and server-side technologies to build personalized user experiences.</p>
<a class="btn btn-primary mt-3" target="_blank"
href="https://www.slideshare.net/Jahia/apache-unomi-project-indepth";>View in
slideshare »</a>
</div>
<div class="col-md-6">
Modified: unomi/website/use-cases.html
URL:
http://svn.apache.org/viewvc/unomi/website/use-cases.html?rev=1908955&r1=1908954&r2=1908955&view=diff
==============================================================================
--- unomi/website/use-cases.html (original)
+++ unomi/website/use-cases.html Tue Apr 4 13:18:11 2023
@@ -104,13 +104,13 @@
<h3 class="font-italic">Use Apache Unomi as an <span
class="text-muted">analytics service</span> for a native mobile application</h3>
<div class="pb-2 pt-2">
- <p>In this case the server is used as a back-end for a native
mobile application that will authenticate a user and then send events to the
server when the user performs certains tasks within the app. Tasks may include
pressing a button, getting close to a location (using GPS or beacons),
etc???</p>
+ <p>In this case the server is used as a back-end for a native
mobile application that will authenticate a user and then send events to the
server when the user performs certains tasks within the app. Tasks may include
pressing a button, getting close to a location (using GPS or beacons),
etcâ¦</p>
<p>The application may also include a UI to expose the privacy
management features of Apache Unomi.</p>
</div>
<h3 class="font-italic">Use Apache Unomi as a <span
class="text-muted">centralized profile management system</span></h3>
<div class="pb-2 pt-2">
- <p>In this use case the server is used a centralized profile
management system, making it easy to aggregate different profile information
that may be stored in different systems such as CRMs, Issue tracking systems,
forums, CMS, ??? One way of achieving this is to make sure that ???anonymous???
profiles are merged when an event such as a login happens and a unique
cross-system identifier (usually the email address) is detected on each
system.</p>
+ <p>In this use case the server is used a centralized profile
management system, making it easy to aggregate different profile information
that may be stored in different systems such as CRMs, Issue tracking systems,
forums, CMS, ⦠One way of achieving this is to make sure that âanonymousâ
profiles are merged when an event such as a login happens and a unique
cross-system identifier (usually the email address) is detected on each
system.</p>
<p>In this case connectors to all the different systems will
need to be developped (and hopefully contributed back to the Apache Unomi
community), so that the centralization of the information is managed by an Open
Source and standards compliant server community.</p>
</div>
</div>
