Hello all, This is a call for vote to release Apache ShardingSphere (Incubating) version 4.0.0-RC1.
The Apache ShardingSphere community has voted on and approved a proposal to release Apache ShardingSphere (Incubating) version 4.0.0-RC1. We now kindly request the Incubator PMC members review and vote on this incubator release. ShardingSphere is an open-source ecosystem consisted of a set of distributed database middleware solutions, including 2 independent products, Sharding-JDBC & Sharding-Proxy. They both provide functions of data sharding, distributed transaction and database orchestration, applicable in a variety of situations such as Java isomorphism, heterogeneous language. Aiming at reasonably making full use of the computation and storage capacity of database in distributed system, ShardingSphere defines itself as a middleware, rather than a totally new type of database. As the cornerstone of many enterprises, relational database still takes a huge market share. Therefore, at current stage, we prefer to focus on its increment instead of a total overturn. Sharding-JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With client end connecting directly to the database, it provides service in the form of jar and requires no extra deployment and dependence. It can be considered as an enhanced JDBC driver, which is fully compatible with JDBC and all kinds of ORM frameworks. * Applicable in any ORM framework based on Java, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC. * Based on any third-party database connection pool, such as DBCP, C3P0, BoneCP, Druid, HikariCP. * Support any kind of database that conforms to JDBC standard: MySQL, Oracle, SQLServer and PostgreSQL for now. Sharding-Proxy defines itself as a transparent database proxy, providing a database server that encapsulates database binary protocol to support heterogeneous languages. Friendlier to DBA, the MySQL/PostgreSQL version provided now can use any kind of client access (such as MySQL Command Client, MySQL Workbench, Navicat etc.) that is compatible of MySQL/PostgreSQL protocol to operate data. * Totally transparent to applications, it can be used directly as MySQL and PostgreSQL. * Applicable to any kind of compatible of client end that is compatible of MySQL and PostgreSQL protocol. ShardingSphere community vote and result thread: https://lists.apache.org/thread.html/7818fb3400ca4404d4d9c47407f4589281ba4a499e0a798b7d714c32@%3Cdev.shardingsphere.apache.org%3E Release notes: https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-d5d2dc137c82994bbaac The release candidates: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC1/ Maven 2 staging repository: https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/ Git tag for the release: https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC1 Release Commit ID: https://github.com/apache/incubator-shardingsphere/commit/2c1d23f9569e5cbe74074a578931c77dfa800800 Keys to verify the Release Candidate: https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS Look at here for how to verify this release candidate: https://shardingsphere.apache.org/community/en/contribute/release/ The vote will be open for at least 72 hours or until necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Checklist for reference: [ ] Download links are valid. [ ] Checksums and PGP signatures are valid. [ ] DISCLAIMER is included. [ ] Source code artifacts have correct names matching the current release. [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo. [ ] All files have license headers if necessary. [ ] No compiled archives bundled in source archive. ------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo
