I agree with you. It doesn't need to be perfect for this RC release. We
also want to release this version as soon as possible.
Unfortunately, there're still 3 serious bugs found in the integration test.
We have to fix them in this version.
So, I'd like to cancel this discussion and prepare for
For a RC release, from my perspective, it doesn’t need to be perfect.
Otherwise, we don’t need RC, we run into GA directly.
I noticed this thread runs into endless trend, I just remind that, we will
always have bug, if it is not serious, and part of models related, I suggest
let RC goes.
I notice a bug about distinct SQL, and create a new issue #2777.
I think we should fix it in RC-2.
--
Yi Yang(Sion)
Apache ShardingSphere
At 2019-07-24 17:36:34, "Zhang Yonglun" wrote:
>Hello ShardingSphere Community,
>
>This is a call for the 3rd round of discussion to release Apache
Moreover, now i have already finished the modification of new APIs and new
features for Encryption module. Considering the modification of APIs, does
anyone think it is better to add this modification to our 4.0.0.RC2?
-
Juan Pan (Trista)
Apache ShardingSphere
#2749 and #2757 are closed, not bug but only questions, we don't need to
modify codes.
More feedback are needed, please feel free to discuss.
zhangli...@apache.org 于2019年7月25日周四 上午11:39写道：
> I notice the issue #2749 and #2757 say boolean value has problem, and this
> problem is caused by
I notice the issue #2749 and #2757 say boolean value has problem, and this
problem is caused by #2604.
We need to research why lots of users report bug on this problem before
vote for release.
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Zhang Yonglun 于2019年7月24日周三
Hello ShardingSphere Community,
This is a call for the 3rd round of discussion to release Apache
ShardingSphere (Incubating) version 4.0.0-RC2
Release notes:
https://github.com/apache/incubator-shardingsphere/releases/tag/untagged-60c0a6418d73359e801e
The release candidates:
