Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

2019-12-26 Thread Juan Pan
Hi Willem, Your reply is what i am waiting for, however could give me more details about this issue? My Max OS is 10.13.6 (17G3025) now, is it needed to update my Max OS to higher version? Juan Pan (Trista) Senior DBA & PPMC of Apache ShardingSphere(Incubating)

Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

2019-12-26 Thread zhangli...@apache.org
OK, we received 2 issues, one for Xcode, one for issue#3770. So we just cancel this release and will release round 2 soon. -- Liang Zhang (John) Apache ShardingSphere & Dubbo Willem Jiang 于2019年12月26日周四 下午9:38写道: > Did you just upgrade your Mac OSX? > I think you need to

Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

2019-12-26 Thread Willem Jiang
Did you just upgrade your Mac OSX? I think you need to install the right version of Xcode to fix the issue. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Dec 24, 2019 at 2:25 PM Juan Pan wrote: > > Hi > > > LICENSE, NOTICE, Checksums and PGP signatures have no problems, however

Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

2019-12-26 Thread Raigor Jiang
I am agree with Sion Yang. On 12/26/2019 18:40,Sion Yang wrote: Sorry, I want to change my vote to -1. I think issue#3770[1] should be fixed and included in 4.0.0 release. ML[2] 4.0.0 stable version release plan also discusses the issue. [1]

Re:Re:[VOTE] Release Apache ShardingSphere (Incubating) 4.0.0

2019-12-26 Thread Sion Yang
Sorry, I want to change my vote to -1. I think issue#3770[1] should be fixed and included in 4.0.0 release. ML[2] 4.0.0 stable version release plan also discusses the issue. [1] https://github.com/apache/incubator-shardingsphere/issues/3770 [2]

Re:4.0.0 stable version release plan

2019-12-26 Thread Raigor Jiang
Agree +1 | | raigor_dev | | raigor_...@163.com | 签名由网易邮箱大师定制 On 12/26/2019 18:29,Sion Yang wrote: I think issue #3770[1] need to be fixed before 4.0.0 stable version. The issue is caused by PR#3663[2]. If we revert PR#3663[2], the encrypt can't only work in JPA with auto-ddl on, and users

Re:4.0.0 stable version release plan

2019-12-26 Thread Sion Yang
I think issue #3770[1] need to be fixed before 4.0.0 stable version. The issue is caused by PR#3663[2]. If we revert PR#3663[2], the encrypt can't only work in JPA with auto-ddl on, and users can avoid this problem by create tables manually. But issue #3770[1] may cause encrypt can't work