diff --git a/CHANGELOG.md b/CHANGELOG.md
index bdfc6f9013f..19b972171a7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,16 @@
 # PD Change Log
 
+## v3.0.0-beta.1
+
++ Unify the log format for easy collection and analysis by tools
++ Simulator
+    - Support different heartbeat intervals in different stores [#1418](https://github.com/pingcap/pd/pull/1418)
+    - Add a case about importing data [#1263](https://github.com/pingcap/pd/pull/1263)
++ Make hotspot scheduling configurable [#1412](https://github.com/pingcap/pd/pull/1412)
++ Add the store address as the dimension monitoring item to replace the previous Store ID [#1429](https://github.com/pingcap/pd/pull/1429)
++ Optimize the `GetStores` overhead to speed up the Region inspection cycle [#1410](https://github.com/pingcap/pd/pull/1410)
++ Add an interface to delete the Tombstone Store [#1472](https://github.com/pingcap/pd/pull/1472)
+
 ## v3.0.0-beta
 - Add `RegionStorage` to store Region metadata separately [#1237](https://github.com/pingcap/pd/pull/1237)
 - Add shuffle hot Region scheduler [#1361](https://github.com/pingcap/pd/pull/1361)
@@ -12,14 +23,14 @@
 - Fix the Region information update issue about Region merge [#1377](https://github.com/pingcap/pd/pull/1377)
 
 ## v2.1.1
-- Fix the issue that some configuration items cannot be set to `0` in the configuration file [#1334](https://github.com/pingcap/pd/pull/1334) 
+- Fix the issue that some configuration items cannot be set to `0` in the configuration file [#1334](https://github.com/pingcap/pd/pull/1334)
 - Check the undefined configuration when starting PD [#1362](https://github.com/pingcap/pd/pull/1362)
 - Avoid transferring the leader to a newly created peer, to optimize the possible delay [#1339](https://github.com/pingcap/pd/pull/1339)
-- Fix the issue that `RaftCluster` cannot stop caused by deadlock [#1370](https://github.com/pingcap/pd/pull/1370) 
+- Fix the issue that `RaftCluster` cannot stop caused by deadlock [#1370](https://github.com/pingcap/pd/pull/1370)
 
 ## v2.1.0
 + Optimize availability
-    - Introduce the version control mechanism and support rolling update of the cluster compatibly 
+    - Introduce the version control mechanism and support rolling update of the cluster compatibly
     - [Enable `Raft PreVote`](https://github.com/pingcap/pd/blob/5c7b18cf3af91098f07cf46df0b59fbf8c7c5462/conf/config.toml#L22) among PD nodes to avoid leader reelection when network recovers after network isolation
     - Enable `raft learner` by default to lower the risk of unavailable data caused by machine failure during scheduling
     - TSO allocation is no longer affected by the system clock going backwards
@@ -34,7 +45,7 @@
     - [Add more commands to control the scheduling policy](https://pingcap.com/docs/tools/pd-control/#config-show--set-option-value)
     - Improve [PD simulator](https://github.com/pingcap/pd/tree/release-2.1/tools/pd-simulator) to simulate the scheduling scenarios
 
-+ API and operation tools 
++ API and operation tools
     - Add the [`GetPrevRegion` interface](https://github.com/pingcap/kvproto/blob/8e3f33ac49297d7c93b61a955531191084a2f685/proto/pdpb.proto#L40) to support the `TiDB reverse scan` feature
     - Add the [`BatchSplitRegion` interface](https://github.com/pingcap/kvproto/blob/8e3f33ac49297d7c93b61a955531191084a2f685/proto/pdpb.proto#L54) to speed up TiKV Region splitting
     - Add the [`GCSafePoint` interface](https://github.com/pingcap/kvproto/blob/8e3f33ac49297d7c93b61a955531191084a2f685/proto/pdpb.proto#L64-L66) to support distributed GC in TiDB
@@ -124,7 +135,7 @@
 * Enable Raft PreVote between PD nodes to avoid leader reelection when network recovers after network isolation
 * Optimize the issue that Balance Scheduler schedules small Regions frequently
 * Optimize the hotspot scheduler to improve its adaptability in traffic statistics information jitters
-* Skip the Regions with a large number of rows when scheduling `region merge` 
+* Skip the Regions with a large number of rows when scheduling `region merge`
 * Enable `raft learner` by default to lower the risk of unavailable data caused by machine failure during scheduling
 * Remove `max-replica` from `pd-recover`
 * Add `Filter` metrics
@@ -133,7 +144,7 @@
 * Fix the issue that TiKV disk space is used up caused by replica migration in some scenarios
 ### Compatibility notes
 * Do not support rolling back to v2.0.x or earlier due to update of the new version storage engine
-* Enable `raft learner` by default in the new version of PD. If the cluster is upgraded from 1.x to 2.1, the machine should be stopped before upgrade or a rolling update should be first applied to TiKV and then PD 
+* Enable `raft learner` by default in the new version of PD. If the cluster is upgraded from 1.x to 2.1, the machine should be stopped before upgrade or a rolling update should be first applied to TiKV and then PD
 
 ## v2.0.4
 ### Improvement