Good news! We can consider about include saga for best effort transaction in ShardingSphere 3.1.0
------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo Willem Jiang <[email protected]> 于2018年12月15日周六 上午10:22写道： > saga-actuator is ready to go after we clean up the license, if > everything is OK we could do the release next week. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Dec 15, 2018 at 9:17 AM [email protected] > <[email protected]> wrote: > > > > Update release plan again ;) > > > > Feature codes are frozen. We are still doing the performance test. > > > > 3.1.0.m1: (20 Dec) > > > > 1. 100% SQL supported if route to single data node. > > 2. XA transaction of Sharding-JDBC. > > 3. Local transaction of Sharding-Proxy. > > > > 3.1.0: (3 Jan) > > 1. bug fix > > > > 4.0.x: (After 3 Jan) > > > > 1. Transfer repo, rename package and maven artifact id to org.apache > > 2. Saga transaction of Sharding-JDBC + Sharding-Proxy (Depends on > > servicecomb-saga 0.3.0 release + one week to integrate). > > 3. Frontend PostgreSQL protocol for Sharding-Proxy > > 4. Use netty to implement backend MySQL protocol for Sharding-Proxy > > (instead of MySQL JDBC) > > > > ------------------ > > > > Liang Zhang (John) > > Apache ShardingSphere & Dubbo > > > > > > [email protected] <[email protected]> 于2018年12月4日周二 上午10:12写道： > > > > > If release 3.1.0 at Dec 15 is the final version of 3.x, maybe need hot > fix > > > on that. So how about release 3.1.0.m1 at Dec 15, and release 3.1.0 > stable > > > version at Dec 31. Then transfer repo to Apache repo? > > > > > > Updated release plan: > > > > > > 3.1.0.m1: (15 Dec) > > > > > > 1. 100% SQL supported if route to single data node. > > > 2. XA transaction of Sharding-JDBC. > > > > > > > > > 3.1.0: (31 Dec) > > > > > > 1. bug fix > > > 2. Local transaction of Sharding-Proxy (If can). > > > > > > > > > 4.0.x: (After 2019 1 Jan) > > > > > > 1. Transfer repo, rename package and maven artifact id to org.apache > > > 2. Saga transaction of Sharding-JDBC + Sharding-Proxy (Depends on > > > servicecomb-saga 0.3.0 release + one week to integrate). > > > 3. Frontend PostgreSQL protocol for Sharding-Proxy > > > 4. Use netty to implement backend MySQL protocol for Sharding-Proxy > > > (instead of MySQL JDBC) > > > 5. Local transaction of Sharding-Proxy (if not released at 3.1.x). > > > > > > ------------------ > > > > > > Liang Zhang (John) > > > Apache Sharding-Sphere & Dubbo > > > > > > > > > Craig Russell <[email protected]> 于2018年12月4日周二 上午9:20写道： > > > > > >> I would suggest it is better to continue to work on 3.x outside of > Apache > > >> with the original package names. Then import into Apache, rename > packages, > > >> and call it 4.0. The rename is a very large undertaking which will > pretty > > >> much mean that porting patches from 3.x will be a challenge. > > >> > > >> But we could also continue to work on features that are now listed > under > > >> 3.x once we import it and rename it. That is, remove items 3, 4, and > 5 from > > >> 3.x and make them features of 4.x. > > >> > > >> If the dates hold, we can import the code into Apache after the Dec 15 > > >> code work is finished. > > >> > > >> The infra JIRA should be updated to let infra know, once we finalize > the > > >> plans. > > >> > > >> Craig > > >> > > >> > On Dec 3, 2018, at 4:32 PM, Willem Jiang <[email protected]> > > >> wrote: > > >> > > > >> > If you don't change the group id, you cannot do the release on the > > >> Apache nexus. > > >> > It look like there could be serval releases of 3.1.x. Are these > > >> > releases Apache release? > > >> > > > >> > Willem Jiang > > >> > > > >> > Twitter: willemjiang > > >> > Weibo: 姜宁willem > > >> > > > >> > On Tue, Dec 4, 2018 at 12:06 AM [email protected] > > >> > <[email protected]> wrote: > > >> >> > > >> >> Change maven article name and group id also need to tell end-users > we > > >> have > > >> >> changed, maybe change them with package together is better, any > idea? > > >> >> > > >> >> ------------------ > > >> >> > > >> >> Liang Zhang (John) > > >> >> Apache Sharding-Sphere & Dubbo > > >> >> > > >> >> > > >> >> 吴晟 Sheng Wu <[email protected]> 于2018年12月3日周一 下午5:49写道： > > >> >> > > >> >>> Feel free to change java package name only in 4. > > >> >>> Also, if you want to do Apache release in 3, you could just change > > >> maven > > >> >>> article name and group id to Apache. This is acceptable. > > >> >>> > > >> >>> > > >> >>> > > >> >>> Sheng Wu > > >> >>> Apache SkyWalking, ShardingSphere, Zipkin > > >> >>> > > >> >>> From Wu Sheng 's phone. > > >> >>> > > >> >>> > > >> >>> ------------------ Original ------------------ > > >> >>> From: [email protected] <[email protected]> > > >> >>> Date: Mon,Dec 3,2018 5:14 PM > > >> >>> To: dev <[email protected]> > > >> >>> Subject: Re: Discuss release plan > > >> >>> > > >> >>> > > >> >>> > > >> >>> Hi, > > >> >>> > > >> >>> I want discuss about release plan for ShardingSphere. We have > roadmap > > >> >>> before join apache incubator, that is: > > >> >>> > http://shardingsphere.jd.com/document/current/img//roadmap_en_v4.png > > >> >>> > > >> >>> Because we are preparing to release distribute transaction > feature at > > >> >>> 3.1.x. If change package name to org.apache, it is better to > release > > >> a new > > >> >>> major version(4.x). So I prefer to discuss release plan. Right > now, > > >> the > > >> >>> release plan is: > > >> >>> > > >> >>> 3.1.x: > > >> >>> > > >> >>> 1. 100% SQL supported if route to single data node (will finish > > >> before dec > > >> >>> 15th). > > >> >>> 2. XA transaction of Sharding-JDBC (will finish before dec 15th). > > >> >>> 3. Local transaction of Sharding-Proxy (No plan yet). > > >> >>> 4. Saga transaction of Sharding-JDBC + Sharding-Proxy (Depends on > > >> >>> servicecomb-saga 0.3.0 release + one week to integrate). > > >> >>> 5. 3.1.x plan to release from 3.0.0.M1, and will release 2~4 > > >> milestomes, > > >> >>> then release 3.1.0 stable version. > > >> >>> > > >> >>> > > >> >>> 4.0.x: > > >> >>> > > >> >>> 1. rename package and maven artifact id to org.apache > > >> >>> 2. Frontend PostgreSQL protocol for Sharding-Proxy > > >> >>> 3. Use netty to implement backend MySQL protocol for > Sharding-Proxy > > >> >>> (instead of MySQL JDBC) > > >> >>> 4. Local transaction of Sharding-Proxy (if not released at 3.1.x). > > >> >>> > > >> >>> Any advice? > > >> >>> > > >> >>> ------------------ > > >> >>> > > >> >>> Liang Zhang (John) > > >> >>> Apache Sharding-Sphere & Dubbo > > >> > > >> Craig L Russell > > >> Secretary, Apache Software Foundation > > >> [email protected] <mailto:[email protected]> http://db.apache.org/jdo < > > >> http://db.apache.org/jdo> > > >> > > > >
