For 3.1.x, I prefer do not for Apache release, just release as before. The
first Apache release strat on 4.0.0

------------------

Liang Zhang (John)
Apache Sharding-Sphere & Dubbo


Willem Jiang <[email protected]> 于2018年12月4日周二 上午8:33写道:

> 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
>

Reply via email to