Add verification system and comparison steps for installation package…

src/UserGuide/Master/Table/Deployment-and-Maintenance/Cluster-Deployment_timecho.md

@@ -57,6 +57,35 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
 
 2. Configure the operating system environment according to [Environment Requirement](../Deployment-and-Maintenance/Environment-Requirements.md)）
 
+### 2.1 Pre-installation Check
+
+To ensure the IoTDB Enterprise Edition installation package you obtained is complete and authentic, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
+
+#### Preparation:
+
+- Obtain the officially released SHA512 checksum: Find the "SHA512 Checksum" corresponding to each version in the [Release History](../IoTDB-Introduction/Release-history_timecho.md) document.
+
+#### Verification Steps (Linux as an Example):
+
+1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
+   ```Bash
+      cd /data/iotdb
+      ```
+2. Execute the following command to calculate the hash value:
+   ```Bash
+      sha512sum timechodb-{version}-bin.zip
+      ```
+3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
+
+![img](/img/sha512-01.png)
+
+4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.
+
+#### Notes:
+
+- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
+- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
+
 ## 3. Installation Steps
 
 Taking a cluster with three Linux servers with the following information as example:
@@ -124,7 +153,7 @@ Set the following parameters in `./conf/iotdb-system.properties`. Refer to `./co
 
 | **Parameter**                   | **Description**                                              | **Default**     | **Recommended**                                                                                                 | **11.101.17.224** | **11.101.17.225** | **11.101.17.226** | **Notes**                                                  |
 | :------------------------------ | :----------------------------------------------------------- |:----------------|:----------------------------------------------------------------------------------------------------------------| :---------------- | :---------------- | :---------------- | :--------------------------------------------------------- |
-| dn_rpc_address                  | Address for the client RPC service                           | 0.0.0.0         | The IPV4 address or host name of the server where it is located, and it is recommended to use the IPV4 address  | iotdb-1           | iotdb-2           | iotdb-3                    | Effective after restarting the service.                    |
+| dn_rpc_address                  | Address for the client RPC service                           | 0.0.0.0         | The IPV4 address or host name of the server where it is located, and it is recommended to use the IPV4 address  | iotdb-1           | iotdb-2           | iotdb-3            | Effective after restarting the service.                    |
 | dn_rpc_port                     | Port for the client RPC service                              | 6667            | 6667                                                                                                            | 6667              | 6667              | 6667              | Effective after restarting the service.                    |
 | dn_internal_address             | Address used for internal communication within the cluster   | 127.0.0.1       | Server's IPv4 address or hostname. Use hostname to avoid issues when the IP changes.                            | iotdb-1           | iotdb-2           | iotdb-3           | This parameter cannot be modified after the first startup. |
 | dn_internal_port                | Port used for internal communication within the cluster      | 10730           | 10730                                                                                                           | 10730             | 10730             | 10730             | This parameter cannot be modified after the first startup. |
@@ -175,8 +204,7 @@ On each server, navigate to the `sbin` directory and start the DataNode:
 
     ```Bash
     show system info
-    ``` 
-
+    ```  
 
 3. Copy the returned machine codes of all nodes in the cluster (displayed as a green string) and send it to the Timecho team:
 

src/UserGuide/Master/Table/Deployment-and-Maintenance/Stand-Alone-Deployment_timecho.md

@@ -48,7 +48,36 @@ Use the hostname for `cn_internal_address` and `dn_internal_address` in IoTDB co
 
 ## 2. Installation Steps
 
-### 2.1 Extract Installation Package
+### 2.1 Pre-installation Check
+
+To ensure the IoTDB Enterprise Edition installation package you obtained is complete and authentic, we recommend performing an SHA512 verification before proceeding with the installation and deployment.
+
+#### Preparation:
+
+- Obtain the officially released SHA512 checksum: Find the "SHA512 Checksum" corresponding to each version in the [Release History](../IoTDB-Introduction/Release-history_timecho.md) document.
+
+#### Verification Steps (Linux as an Example):
+
+1. Open the terminal and navigate to the directory where the installation package is stored (e.g., /data/iotdb):
+   ```Bash
+      cd /data/iotdb
+      ```
+2. Execute the following command to calculate the hash value:
+   ```Bash
+      sha512sum timechodb-{version}-bin.zip
+      ```
+3. The terminal will output a result (the left part is the SHA512 checksum, and the right part is the file name):
+
+![img](/img/sha512-01.png)
+
+4. Compare the output result with the official SHA512 checksum. Once confirmed that they match, you can proceed with the installation and deployment operations in accordance with the procedures below.
+
+#### Notes:
+
+- If the verification results do not match, please contact Timecho Team to re-obtain the installation package.
+- If a "file not found" prompt appears during verification, check whether the file path is correct or if the installation package has been fully downloaded.
+
+### 2.2 Extract Installation Package
 
 Unzip the installation package and navigate to the directory:
 
@@ -57,9 +86,9 @@ unzip timechodb-{version}-bin.zip
 cd timechodb-{version}-bin
 ```
 
-### 2.2 Parameters Configuration
+### 2.3 Parameters Configuration
 
-#### 2.2.1 Memory Configuration
+#### 2.3.1 Memory Configuration
 
 Edit the following files for memory allocation:
 
@@ -70,7 +99,7 @@ Edit the following files for memory allocation:
 | :------------ | :---------------------------------- | :---------- | :-------------- | :---------------------- |
 | MEMORY_SIZE   | Total memory allocated for the node | Empty       | As needed       | Save changes without immediate execution; modifications take effect after service restart. |
 
-#### 2.2.2 General Configuration
+#### 2.3.2 General Configuration
 
 Set the following parameters in `conf/iotdb-system.properties`. Refer to `conf/iotdb-system.properties.template` for a complete list.
 
@@ -104,7 +133,7 @@ Set the following parameters in `conf/iotdb-system.properties`. Refer to `conf/i
 | dn_schema_region_consensus_port | Port used for metadata replica consensus protocol communication | 10760           | 10760                                                                                                           | This parameter cannot be modified after the first startup. |
 | dn_seed_config_node             | Address of the ConfigNode for registering and joining the cluster. (e.g.,`cn_internal_address:cn_internal_port`) | 127.0.0.1:10710 | Use `cn_internal_address:cn_internal_port`                                                                      | This parameter cannot be modified after the first startup. |
 
-### 2.3 Start ConfigNode
+### 2.4 Start ConfigNode
 
 Navigate to the `sbin` directory and start ConfigNode:
 
@@ -116,15 +145,15 @@ If the startup fails, refer to the [Common Issues](#3-common-issues)。 section
 
 
 
-### 2.4 Start DataNode
+### 2.5 Start DataNode
 
 Navigate to the `sbin` directory of IoTDB and start the DataNode:
 
 ```Bash
 ./sbin/start-datanode.sh -d    # The "-d" flag starts the process in the background.
 ```
 
-### 2.5 Activate the Database
+### 2.6 Activate the Database
 
 #### Option 1: Command-Based Activation
 
@@ -162,16 +191,14 @@ It costs 0.030s
 IoTDB> activate '01-D4EYQGPZ-EAUJJODW-NUKRDR6F-TUQS3B75-EDZFLK3A-6BOKJFFZ-ALDHOMN7-NB2E4BHI-7ZKGFVK6-GCIFXA4T-UG3XJTTD-SHJV6F2P-Q27B4OMJ-R47ZDIM3-UUASUXG2-OQXGVZCO-MMYKICZU-TWFQYYAO-ZOAGOKJA-NYHQTA5U-EWAR4EP5-MRC6R2CI-PKUTKRCT-7UDGRH3F-7BYV4P5D-6KKIA==='
 ```
 
-
 #### Option 2: File-Based Activation
 
 - Start both the ConfigNode and DataNode.
 - Navigate to the `activation` folder and copy the `system_info` file.
 - Send the `system_info` file to the Timecho team.
 - Place the license file provided by the Timecho team into the corresponding `activation` folder for each node.
 
-
-### 2.6 Verify Activation
+### 2.7 Verify Activation
 
 In the CLI, you can check the activation status by running the `show activation` command. Check the `ClusterActivationStatus` field. If it shows `ACTIVATED`, the database has been successfully activated.
 

src/UserGuide/Master/Table/IoTDB-Introduction/Release-history_apache.md

@@ -20,9 +20,25 @@
 -->
 # Release History
 
+
+## V2.0.5
+
+> Release Date: 2025.08.21
+
+V2.0.5, as the official release of the Dual-Model Tree-Table system, primarily introduces the tree-to-table view, window functions for the table model, the aggregate function approx_most_frequent, and supports LEFT & RIGHT JOIN as well as ASOF LEFT JOIN. The AINode now includes two new built-in models, Timer-XL and Timer-Sundial, and supports inference capabilities for both tree and table models. Additionally, this version brings comprehensive improvements to database monitoring, performance, and stability. The specific updates are as follows:
+
+* **Query Module**: Supports manual creation of tree-to-table views
+* **Query Module**: Adds window functions for the table model
+* **Query Module**: Adds the aggregate function approx_most_frequent for the table model
+* **Query Module**: Extends JOIN functionality for the table model, supporting LEFT & RIGHT JOIN and ASOF LEFT JOIN
+* **Query Module**: The table model now supports row pattern recognition, enabling the capture of continuous data for analysis and computation
+* **Storage Module**: Adds multiple system tables for the table model, such as VIEWS (table view information) and MODELS (model information)
+* **AI Module**: AINode adds two new built-in models, Timer-XL and Timer-Sundial
+* **AI Module**: AINode supports inference functions for both tree and table models
+
 ## V2.0.4
 
-> Release Time: 2025.07.09
+> Release Date: 2025.07.09
 
 V2.0.4 serves as the official release of the dual-model system for tree and table structures. The table model primarily introduces user-defined table functions (UDTF) and multiple built-in table functions, adds the aggregate function approx_count_distinct, and supports ASOF INNER JOIN for time columns. Additionally, script tools have been categorized and reorganized, with Windows-specific scripts separated. The release also includes comprehensive improvements in database monitoring, performance, and stability. The detailed updates are as follows:
 
@@ -106,6 +122,12 @@ V2.0.1-beta introduces dual tree-table model configuration, supporting standard
 * ​**​Ecosystem Integration​**​:
     * Kubernetes Operator support
 
+## V1.3.5
+
+> Release Date: 2025.09.12
+
+V1.3.5, as a bugfix release based on the previous 1.3.x versions, primarily adjusts the user password encryption algorithm to further enhance data access security. It also optimizes kernel stability and addresses issues reported by the community.
+
 
 ## V1.3.4