Modified: unomi/website/contribute/release-guide.html URL: http://svn.apache.org/viewvc/unomi/website/contribute/release-guide.html?rev=1898483&r1=1898482&r2=1898483&view=diff ============================================================================== --- unomi/website/contribute/release-guide.html (original) +++ unomi/website/contribute/release-guide.html Mon Feb 28 16:01:37 2022 @@ -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: 1.6.0. - Ideally all tickets listed for version: 1.6.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.0.0. + Ideally all tickets listed for version: 2.0.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: 1.6.0. It will be useful for linking the release notes in the voting mail. + By choosing the version: 2.0.0. It will be useful for linking the release notes in the voting mail. </li> </ol> @@ -247,13 +247,13 @@ git checkout -b unomi-1.6.x as it is required to build everything. </li> <li>Tests source, javadocs, docker and signature generation using: - <pre class="alert alert-primary"><code>mvn clean install -P apache-release,performance-tests,integration-tests,docker</code></pre> + <pre class="alert alert-primary"><code>mvn clean install -P apache-release,integration-tests,docker</code></pre> </li> <li>Make sure we generate all sub-projects using: - <pre class="alert alert-primary"><code>mvn clean install -DskipITs=true -DskipTests=true -P integration-tests,performance-tests,rat,apache-release,docker,\!run-tests</code></pre> + <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-1.6.0-SNAPSHOT.rat</code></pre> + <pre class="alert alert-primary"><code>less target/unomi-root-2.0.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) @@ -278,19 +278,18 @@ gpg: signing failed: Inappropriate ioctl <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>Check into the target directory and unzip the source release and compile it using: - <pre class="alert alert-primary"><code>pushd -cd target -gpg --verify unomi-root-1.6.0-SNAPSHOT-source-release.zip.asc unomi-root-1.6.0-SNAPSHOT-source-release.zip -shasum -a 512 unomi-root-1.6.0-SNAPSHOT-source-release.zip -cat unomi-root-1.6.0-SNAPSHOT-source-release.zip.sha512 -unzip unomi-root-1.6.0-SNAPSHOT-source-release.zip -cd unomi-root-1.6.0-SNAPSHOT + <pre class="alert alert-primary"><code>pushd target +gpg --verify unomi-root-2.0.0-SNAPSHOT-source-release.zip.asc unomi-root-2.0.0-SNAPSHOT-source-release.zip +shasum -a 512 unomi-root-2.0.0-SNAPSHOT-source-release.zip +cat unomi-root-2.0.0-SNAPSHOT-source-release.zip.sha512 +unzip unomi-root-2.0.0-SNAPSHOT-source-release.zip +cd unomi-root-2.0.0-SNAPSHOT mvn clean install popd</code></pre> to check that the packaged source build properly </li> <li>Go back to the root project directory (pushd/popd did that for you normally) and run: - <pre class="alert alert-primary"><code>mvn release:prepare -DskipITs=true -DskipTests=true -Drelease.arguments="-Papache-release,integration-tests -DskipITs=true -DskipTests=true" -DdryRun=true -P apache-release,integration-tests,performance-tests,docker,\!run-tests</code></pre> + <pre class="alert alert-primary"><code>mvn release:prepare -DskipITs=true -DskipTests=true -Drelease.arguments="-Papache-release,integration-tests -DskipITs=true -DskipTests=true" -DdryRun=true -P apache-release,integration-tests,docker,\!run-tests</code></pre> </li> <li>Publish a snapshot to test the deployment passwords: <pre class="alert alert-primary"><code>mvn deploy -DskipITs=true -DskipTests=true -P \!run-tests</code></pre> @@ -299,20 +298,20 @@ popd</code></pre> <pre class="alert alert-primary"><code>rm release.properties</code></pre> </li> <li> - <pre class="alert alert-primary"><code>mvn -P apache-release,integration-tests,performance-tests,docker,\!run-tests release:prepare</code></pre> + <pre class="alert alert-primary"><code>mvn -P apache-release,integration-tests,docker,\!run-tests release:prepare</code></pre> </li> <li> - <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,performance-tests,\!run-tests release:perform</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: <pre class="alert alert-primary"><code>scm.url=scm:git:https://gitbox.apache.org/repos/asf?p=unomi.git -scm.tag=unomi-root-1.6.0 +scm.tag=unomi-root-2.0.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 1.6.0 Release Candidate 1</strong> + <strong>Apache Unomi 2.0.0 Release Candidate 1</strong> </li> </ol> @@ -323,56 +322,57 @@ and run mvn release:perform</code></pre> </li> <li> <pre class="alert alert-primary"><code>cd unomi-dev -mkdir 1.6.0</code></pre> +mkdir 2.0.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/1.6.0/" target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/1.6.0/</a> + <a href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.0.0/" target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/2.0.0/</a> and - <a href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/1.6.0/" target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/1.6.0/</a> - using commands such as : <pre class="alert alert-primary"><code>wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi-root/1.6.0/unomi-root-1.6.0-source-release.zip -wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi-root/1.6.0/unomi-root-1.6.0-source-release.zip.asc -wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi/1.6.0/unomi-1.6.0.tar.gz -wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi/1.6.0/unomi-1.6.0.tar.gz.asc -wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi/1.6.0/unomi-1.6.0.zip -wget https://repository.apache.org/content/repositories/orgapacheunomi-1030/org/apache/unomi/unomi/1.6.0/unomi-1.6.0.zip.asc</code></pre> + <a href="https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.0.0/" target="_blank">https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/2.0.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.0.0/unomi-root-2.0.0-source-release.zip +wget https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi-root/2.0.0/unomi-root-2.0.0-source-release.zip.asc +wget https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.0.0/unomi-2.0.0.tar.gz +wget https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.0.0/unomi-2.0.0.tar.gz.asc +wget https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.0.0/unomi-2.0.0.zip +wget https://repository.apache.org/content/repositories/$REPO_ID/org/apache/unomi/unomi/2.0.0/unomi-2.0.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-1.6.0-source-release.zip unomi-1.6.0-src.zip -mv unomi-root-1.6.0-source-release.zip.asc unomi-1.6.0-src.zip.asc -shasum -a 512 unomi-1.6.0-src.zip > unomi-1.6.0-src.zip.sha512 - -mv unomi-1.6.0.zip unomi-1.6.0-bin.zip -mv unomi-1.6.0.zip.asc unomi-1.6.0-bin.zip.asc -shasum -a 512 unomi-1.6.0-bin.zip > unomi-1.6.0-bin.zip.sha512 - -mv unomi-1.6.0.tar.gz unomi-1.6.0-bin.tar.gz -mv unomi-1.6.0.tar.gz.asc unomi-1.6.0-bin.tar.gz.asc -shasum -a 512 unomi-1.6.0-bin.tar.gz > unomi-1.6.0-bin.tar.gz.sha512 +mv unomi-root-2.0.0-source-release.zip unomi-2.0.0-src.zip +mv unomi-root-2.0.0-source-release.zip.asc unomi-2.0.0-src.zip.asc +shasum -a 512 unomi-2.0.0-src.zip > unomi-2.0.0-src.zip.sha512 + +mv unomi-2.0.0.zip unomi-2.0.0-bin.zip +mv unomi-2.0.0.zip.asc unomi-2.0.0-bin.zip.asc +shasum -a 512 unomi-2.0.0-bin.zip > unomi-2.0.0-bin.zip.sha512 + +mv unomi-2.0.0.tar.gz unomi-2.0.0-bin.tar.gz +mv unomi-2.0.0.tar.gz.asc unomi-2.0.0-bin.tar.gz.asc +shasum -a 512 unomi-2.0.0-bin.tar.gz > unomi-2.0.0-bin.tar.gz.sha512 </code></pre> </li> <li> <pre class="alert alert-primary"><code>cd .. -svn add 1.6.0</code></pre> +svn add 2.0.0</code></pre> </li> <li> - <pre class="alert alert-primary"><code>svn commit -m "Apache 1.6.0 Release (for PMC voting)"</code></pre> + <pre class="alert alert-primary"><code>svn commit -m "Apache 2.0.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-1.6.0 -git tag -d unomi-root-1.6.0</code></pre> + <pre class="alert alert-primary"><code>git push --delete origin unomi-root-2.0.0 +git tag -d unomi-root-2.0.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: - <pre class="alert alert-primary"><code>mvn versions:set -DskipITs=true -DskipTests=true -P integration-tests,performance-tests,rat,apache-release,docker,\!run-tests</code></pre> + <pre class="alert alert-primary"><code>mvn versions:set -DskipITs=true -DskipTests=true -P integration-tests,rat,apache-release,docker,\!run-tests</code></pre> </li> <li>Restart at the release:prepare step</li> </ol> @@ -391,7 +391,7 @@ git tag -d unomi-root-1.6.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/1.6.0 https://dist.apache.org/repos/dist/release/unomi/1.6.0 -m "Apache Unomi 1.6.0 Release"</code></pre> + <pre class="alert alert-primary"><code>svn mv https://dist.apache.org/repos/dist/dev/unomi/2.0.0 https://dist.apache.org/repos/dist/release/unomi/2.0.0 -m "Apache Unomi 2.0.0 Release"</code></pre> </li> <li> In JIRA mark the version as released and add a release date @@ -413,18 +413,18 @@ git tag -d unomi-root-1.6.0</code></pre> </li> <li> Test the site modifications using the generated site HTML using Jekyll serve - <pre class="alert alert-primary"><code>mvn clean install gem:exec@jekyll-serve-filtered</code></pre> + <pre class="alert alert-primary"><code>mvnw clean install gem:exec@jekyll-serve-filtered</code></pre> Connect to http://127.0.0.1:4000 to check the modifications. If you need to make more modifications, simply relaunch the above line after modifying the HTML files. </li> <li> Deploy the web site changes using: - <pre class="alert alert-primary"><code>mvn clean install -mvn install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME -Dpassword=YOUR_APACHE_PASSWORD</code></pre> + <pre class="alert alert-primary"><code>mvnw clean install +mvnw install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME -Dpassword=YOUR_APACHE_PASSWORD</code></pre> </li> <li> Then make sure to commit all the changes to the web site's git project: - <pre class="alert alert-primary"><code>git commit -m "Apache Unomi 1.6.0 Release website update"</code></pre> + <pre class="alert alert-primary"><code>git commit -m "Apache Unomi 2.0.0 Release website update"</code></pre> </li> </ol> @@ -442,14 +442,14 @@ mvn install scm-publish:publish-scm -Dus 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/1.6.0 -mv unomi-manual-1_6_x.pdf 1.6.0 -mv unomi-manual-1_6_x.pdf.asc 1.6.0 -mv unomi-manual-1_6_x.zip 1.6.0 -mv unomi-manual-1_6_x.pdf.sha512 1.6.0 -mv unomi-manual-1_6_x.zip.asc 1.6.0 -mv unomi-manual-1_6_x.zip.sha512 1.6.0 -cd 1.6.0 +svn co https://dist.apache.org/repos/dist/release/unomi/2.0.0 +mv unomi-manual-1_6_x.pdf 2.0.0 +mv unomi-manual-1_6_x.pdf.asc 2.0.0 +mv unomi-manual-1_6_x.zip 2.0.0 +mv unomi-manual-1_6_x.pdf.sha512 2.0.0 +mv unomi-manual-1_6_x.zip.asc 2.0.0 +mv unomi-manual-1_6_x.zip.sha512 2.0.0 +cd 2.0.0 svn add unomi-manual* svn commit -m "Update Unomi manual packages"</code></pre> </li> @@ -460,7 +460,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-1.6.0</code></pre> + <pre class="alert alert-primary"><code>git checkout tags/unomi-root-2.0.0</code></pre> </li> <li> Change to the Docker directory. Make sure you have docker running locally (start Docker Desktop for @@ -478,8 +478,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-1.6.0 -git tag --delete unomi-root-1.6.0</code></pre> + <pre class="alert alert-primary"><code>git push --delete origin unomi-root-2.0.0 +git tag --delete unomi-root-2.0.0</code></pre> </li> <li>Reset to the previous commit before the release preparation: <pre class="alert alert-primary"><code>git reset --hard c65f9897ec5f31d9d22ad639738c7db9d109aa77 @@ -529,11 +529,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 1.6.0 release [TAKE2] +Subject: [VOTE] Apache Unomi 2.0.0 release [TAKE2] Body: Hi all, -I submit Apache Unomi 1.6.0 release [TAKE2] to your vote. +I submit Apache Unomi 2.0.0 release [TAKE2] to your vote. The following corrections were done since TAKE 1: NOTICE year (2016) has been updated to 2018 @@ -547,18 +547,18 @@ Staging Repository: You can find the sources here : *https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/ -unomi/unomi-root/1.6.0/unomi-root-1.6.0-source-release.zip +unomi/unomi-root/2.0.0/unomi-root-2.0.0-source-release.zip <https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/ -unomi/unomi-root/1.6.0/unomi-root-1.6.0-source-release.zip>* +unomi/unomi-root/2.0.0/unomi-root-2.0.0-source-release.zip>* Convenience binaries are also available here: *https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/ -unomi/unomi/1.6.0/ +unomi/unomi/2.0.0/ <https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/ -unomi/unomi/1.6.0/>* +unomi/unomi/2.0.0/>* Git tag: -unomi-root-1.6.0 +unomi-root-2.0.0 Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220& @@ -580,7 +580,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 1.6.0 release [TAKE2] +Subject: [RESULT][VOTE] Apache Unomi 2.0.0 release [TAKE2] Body: Hi, @@ -600,7 +600,7 @@ John Doe 5 No 0 or -1. -The proposal to release Unomi 1.6.0 is approved by the team. +The proposal to release Unomi 2.0.0 is approved by the team. Thanks, John Doe 1 @@ -608,10 +608,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 1.6.0 Release +Subject : [ANNOUNCE] Apache Unomi 2.0.0 Release Body: The Apache Unomi team would like to announce the release of Apache -Unomi 1.6.0. +Unomi 2.0.0. Release notes are here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220& @@ -625,10 +625,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/1.6.0/ +https://dist.apache.org/repos/dist/release/incubator/unomi/2.0.0/ All JIRAs completed for this release are tagged with 'FixVersion = -1.6.0'; the JIRA release notes can be found here: +2.0.0'; the JIRA release notes can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220& version=12338361
Modified: unomi/website/download.html URL: http://svn.apache.org/viewvc/unomi/website/download.html?rev=1898483&r1=1898482&r2=1898483&view=diff ============================================================================== --- unomi/website/download.html (original) +++ unomi/website/download.html Mon Feb 28 16:01:37 2022 @@ -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">1.5.7</span></h3> - <div class="mb-1 text-muted">July 27th, 2021</div> + <h3 class="mb-0 text-dark">Unomi <span class="text-muted">1.6.0</span></h3> + <div class="mb-1 text-muted">February 28th, 2022</div> <p class="card-text mb-auto"> Binary Distribution : - <a target="_blank" href="https://www.apache.org/dyn/closer.lua/unomi/1.5.7/unomi-1.5.7-bin.tar.gz">tar.gz</a> - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.tar.gz.asc">PGP</a>] - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.tar.gz.sha512">SHA512</a>] - - <a target="_blank" href="https://www.apache.org/dyn/closer.lua/unomi/1.5.7/unomi-1.5.7-bin.zip">zip</a> - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.zip.asc">PGP</a>] - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.zip.sha512">SHA512</a>] + <a target="_blank" href="https://www.apache.org/dyn/closer.lua/unomi/1.6.0/unomi-1.6.0-bin.tar.gz">tar.gz</a> + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.0-bin.tar.gz.asc">PGP</a>] + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.0-bin.tar.gz.sha512">SHA512</a>] - + <a target="_blank" href="https://www.apache.org/dyn/closer.lua/unomi/1.6.0/unomi-1.6.0-bin.zip">zip</a> + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.0-bin.zip.asc">PGP</a>] + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.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/1.5.7/unomi-1.5.7-src.zip">zip</a> - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-src.zip.asc">PGP</a>] - [<a target="_blank" href="https://www.apache.org/dist/unomi/1.5.7/unomi-1.5.7-src.zip.sha512">SHA512</a>] + <a target="_blank" href="https://www.apache.org/dyn/closer.lua/unomi/1.6.0/unomi-1.6.0-src.zip">zip</a> + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.0-src.zip.asc">PGP</a>] + [<a target="_blank" href="https://www.apache.org/dist/unomi/1.6.0/unomi-1.6.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=12350150" 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=12350121" role="button" target="_blank">Release notes »</a> </div> </div> </div> @@ -136,7 +136,7 @@ </code> <br> <code> - % gpg --verify unomi-1.5.7-bin.tar.gz.asc unomi-1.5.7-bin.tar.gz + % gpg --verify unomi-1.6.0-bin.tar.gz.asc unomi-1.6.0-bin.tar.gz </code> </p> </div> @@ -160,6 +160,33 @@ </thead> <tbody> <tr> + <td>1.5.7</td> + <td><a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.tar.gz">tar.gz</a> + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.tar.gz.asc">PGP</a>] + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.tar.gz.sha512">SHA512</a>]<br> + <a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.zip">zip</a> + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.zip.asc">PGP</a>] + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-bin.zip.sha512">SHA512</a>] + </td> + <td> + <a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-src.zip">zip</a> + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-src.zip.asc">PGP</a>] + [<a target="_blank" + href="https://archive.apache.org/dist/unomi/1.5.7/unomi-1.5.7-src.zip.sha512">SHA512</a>] + </td> + <td><a target="_blank" + href=""https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&version=12350150">Release + Notes</a></td> + </tr> + <tr> <td>1.5.6</td> <td><a target="_blank" href="https://archive.apache.org/dist/unomi/1.5.6/unomi-1.5.6-bin.tar.gz">tar.gz</a> Modified: unomi/website/index.html URL: http://svn.apache.org/viewvc/unomi/website/index.html?rev=1898483&r1=1898482&r2=1898483&view=diff ============================================================================== --- unomi/website/index.html (original) +++ unomi/website/index.html Mon Feb 28 16:01:37 2022 @@ -103,18 +103,45 @@ <h1 class="mb-5">News</h1> + <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> + </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> + </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 --> + + <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 the agenda, registration and more details on the <a href="/community/events/meetups/2021-11-18.html">event's page</a>.</p> + <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"> <h3>First Apache Unomi meetup !</h3> <p> - Join us for the first ever (online) community meetup of the Apache Unomi CDP project organized by the Apache - project management committee (PMC) on <strong>Nov 18th, 2021 from 1600 to 1800 CET</strong> and learn about API-first open-source - customer data, analytics and personalization! + 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 -->
