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

fanningpj pushed a commit to branch main
in repository 
https://gitbox.apache.org/repos/asf/incubator-pekko-persistence-r2dbc.git


The following commit(s) were added to refs/heads/main by this push:
     new 2f3148b  Update README.md (#75)
2f3148b is described below

commit 2f3148becf577293d4286a4f2f9196bbb0c84f92
Author: PJ Fanning <[email protected]>
AuthorDate: Wed Dec 27 17:15:30 2023 +0100

    Update README.md (#75)
    
    * Update README.md
    
    after 1.0.0 release
    
    * Update README.md
---
 README.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 329c0f7..cf658ec 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,20 @@ store for SQL databases with RD2BC connectivity.
 
 ## Project status
 
-Under development.
+Version 1.0.0 has been released. Any contributions are welcome. Please observe 
the [Code of 
Conduct](https://github.com/apache/incubator-pekko-persistence-r2dbc?tab=coc-ov-file#readme).
+
+## Documentation
+
+* [Current Apache Pekko PersistenceR2JDBC 
documentation](https://pekko.apache.org/docs/pekko-persistence-r2dbc/current/)
+
+## Community
+
+There are several ways to interact with the Pekko community:
+
+- [GitHub 
discussions](https://github.com/apache/incubator-pekko-persistence-jdbc/discussions):
 for questions and general discussion.
+- [Pekko dev mailing 
list](https://lists.apache.org/[email protected]): for Pekko 
development discussions.
+- [Pekko users mailing 
list](https://lists.apache.org/[email protected]): for Pekko 
user discussions.
+- [GitHub 
issues](https://github.com/apache/incubator-pekko-persistence-r2dbc/issues): 
for bug reports and feature requests. Please search the existing issues before 
creating new ones. If you are unsure whether you have found a bug, consider 
asking in GitHub discussions or the mailing list first.
 
 ## License
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to