This is an automated email from the ASF dual-hosted git repository.

jxue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/helix.git


The following commit(s) were added to refs/heads/master by this push:
     new 83c1008  Add release note for 1.0.0
83c1008 is described below

commit 83c1008bba62797b36c2199400a613f6c64d43fe
Author: Junkai Xue <[email protected]>
AuthorDate: Mon May 4 17:19:41 2020 -0700

    Add release note for 1.0.0
---
 website/1.0.0/pom.xml                              |  4 +--
 .../src/site/apt/releasenotes/release-1.0.0.apt    | 37 +++++++++++++++++++---
 website/pom.xml                                    |  1 +
 3 files changed, 36 insertions(+), 6 deletions(-)

diff --git a/website/1.0.0/pom.xml b/website/1.0.0/pom.xml
index aa00b15..f58af08 100644
--- a/website/1.0.0/pom.xml
+++ b/website/1.0.0/pom.xml
@@ -26,9 +26,9 @@ under the License.
     <version>0.9.2-SNAPSHOT</version>
   </parent>
 
-  <artifactId>0.9.1-docs</artifactId>
+  <artifactId>1.0.0-docs</artifactId>
   <packaging>bundle</packaging>
-  <name>Apache Helix :: Website :: 0.9.1</name>
+  <name>Apache Helix :: Website :: 1.0.0</name>
 
   <properties>
   </properties>
diff --git a/website/1.0.0/src/site/apt/releasenotes/release-1.0.0.apt 
b/website/1.0.0/src/site/apt/releasenotes/release-1.0.0.apt
index c93d878..13ab3df 100644
--- a/website/1.0.0/src/site/apt/releasenotes/release-1.0.0.apt
+++ b/website/1.0.0/src/site/apt/releasenotes/release-1.0.0.apt
@@ -36,13 +36,42 @@ Release Notes for Apache Helix 1.0.0
 
 * Key Note for Helix Release
 
-** Major Feature Support
+** ZooScalability
 
-*** ZooScalability
+   Project ZooScalability includes initiatives and newly-added components to 
achieve horizontal scalability of ZooKeeper. Some Helix applications have been 
experiencing performance loss due to increased traffic to ZooKeeper.
 
-*** Helix Cloud Support
+** Helix Cloud Support
+
+    Helix new features for customers in a cloud environment, e.g. Azure, AWS, 
or GCP, etc. This version implements the function of participant auto 
registration to a Helix cluster, using Azure cloud provider as an example. With 
this feature, after a Helix cluster is created, the participant can auto 
register itself to the cluster when the participant comes online. Users do not 
need to manually populate any information, even the fault domain information, 
which can be dynamically retrieved [...]
+
+    Detailed wiki page: 
{{https://github.com/apache/helix/wiki/Helix-Cloud-Support}}
+
+** Customized View Aggregation
+
+    A new feature for customers to define their own per partition state and 
provides aggregated view for the customized states. The customized state is 
updated by customers on demand and stored under each participant’s customized 
state path. Depending on a new cluster level config, called customized state 
config, Helix generic controller decides whether it will do aggregation across 
all participants on the state or not. If aggregation on a certain state is 
turned on, the output will be o [...]
+
+    For details: 
{{https://github.com/apache/helix/wiki/Customized-View-Aggregation}}
+
+** Distributed Lock Support
+
+    An exclusive distributed lock based on ZooKeeper for Helix users to 
coordinate their work on the same resource. Currently we support:
+
+    * Synchronized lock: Acquires the lock if it is available immediately 
returns true, and lock path znode is updated with the new lock data (owner id, 
timeout stamp, etc.). If the user is already the lock owner, returns true. If 
the lock is not available then immediately return false.
+
+    * Synchronized unlock: Lock owner can unlock the lock and set the lock 
path znode data to default data (empty owner id, empty message, etc).
+
+    * Lock timeout: User provides an expiration time for the lock while 
acquiring it. The lock automatically becomes available after this timestamp. 
Any user can query the lock information and check when the lock will be expired.
+
+    * Lock message: Lock owner can provide a message for other users to know 
the purpose of current lock. Lock messages can be retrieved when users query 
the lock information.
+
+    * Lock owner recognition: Users can check if they are the current lock 
owner of a certain path.
+
+** Weight Aware Global Even Distribute Rebalancer
+
+    A new weight-aware globally-even distribute Rebalancer to better meet the 
applications’ requirement.
+
+    Please refer to 
{{https://github.com/apache/helix/wiki/Weight-aware-Globally-Evenly-distributed-Rebalancer.}}
 
-*** Weight Aware Global Even Distribute Rebalancer
 
 []
 
diff --git a/website/pom.xml b/website/pom.xml
index 823f34a..0a4e9d6 100644
--- a/website/pom.xml
+++ b/website/pom.xml
@@ -50,6 +50,7 @@ under the License.
     <module>0.8.4</module>
     <module>0.9.0</module>
     <module>0.9.1</module>
+    <module>1.0.0</module>
   </modules>
 
   <properties>

Reply via email to