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

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


The following commit(s) were added to refs/heads/master by this push:
     new a9c193a  Update README.md (#13566)
a9c193a is described below

commit a9c193af6ae69ae4e9e53f448ecb8999a6c91215
Author: Yacine Si Tayeb <[email protected]>
AuthorDate: Fri Nov 12 14:14:56 2021 +0800

    Update README.md (#13566)
    
    Added nightly builds.
---
 README.md | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c40e2ea..65ec405 100644
--- a/README.md
+++ b/README.md
@@ -57,12 +57,24 @@ For guides on how to get started and setup your 
environment, contributor & commi
 
 ## Status:
 
-:white_check_mark: Version 5.0.0: released, stable enough & anyone can sign up 
:tada:
+:white_check_mark: Version 5.0.0: released :tada:
+
+🔗 For the release notes, follow this link to the relevant [GitHub 
page](https://github.com/apache/shardingsphere/blob/master/RELEASE-NOTES.md).
+
 
 :soon: Version 5.0.1
 
 We are currently working towards our 5.0.1 milestone. Keep an eye on the 
[milestones page](https://github.com/apache/shardingsphere/milestones) of this 
repo to stay up to date.
 
+
+ ## Nightly Builds:
+
+ A nightly build of ShardingSphere from the latest master branch is available. 
The package is updated daily and is [available here](http://117.48.121.24:8080).
+
+ #### ‼️ Notice: 
+
+ Use this nightly build at your own risk! The branch is not always fully 
tested. The nightly build may contain bugs, and there may be new features added 
which may cause problems with your environment. 
+
 ## How it Works:
 
 Apache ShardingSphere includes 3 independent products: JDBC, Proxy & Sidecar 
(Planning). They all provide functions of data scale-out, distributed 
transaction and distributed governance, applicable in a variety of situations 
such as Java isomorphism, heterogeneous language and Cloud-Native.

Reply via email to