I agree with you. The performance data is the most important aspect, should
be finished before others.
Zhang Yonglun
Apache ShardingSphere
zhangli...@apache.org 于2019年12月9日周一 下午2:31写道：
> These 3 tasks are good enough for finish all performance test issue. I
> think they should not as block
Hi,
> What features will be planned in pluggable platform?
There is no new feature of pluggable platform. We just need redesign the
current framework to make it more flexible.
> And how to assign features splits from sharding-core?
As the new design, sharding-core is not a mandatory feature,
These 3 tasks are good enough for finish all performance test issue. I
think they should not as block issues of release.
How about change the block issue as know the actual performance data?
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Zhang Yonglun 于2019年12月9日周一
> +1 Love the idea. Just feeling the project name(Sharding) will be the
bottleneck :P
Sharding is a brand of previous name (Sharding-JDBC), because JDBC is not
suitable with our project, so we keep the first word as brand and just
change the last word to `Sphere`.
Maybe we can talk about change
+1 Love the idea. Just feeling the project name(Sharding) will be the
bottleneck :P
Sheng Wu 吴晟
Twitter, wusheng1108
zhangli...@apache.org 于2019年12月9日周一 下午1:30写道：
> Hi, ShardingSphere community,
>
> More and more features are added into ShardingSphere now, as you know, the
> scope of
Hi, ShardingSphere community,
More and more features are added into ShardingSphere now, as you know, the
scope of ShardingSphere is no longer for sharding only.
There are more and more features related with sharding, such as distributed
transaction, distributed orchestration, observability and so
Hi,
Since the performance test display is so important that has impacted the
4.0.0 release. All the work below should be finished by the end of this
week.
1. Add a scenario for Master-Slave. r/w to the same database compare with
r/w split.
2. Describe the testing scenario in detail, including
Liang,
You are right. I'll create a schedule for performance test.
Zhang Yonglun
Apache ShardingSphere
zhangli...@apache.org 于2019年12月9日周一 上午11:34写道：
> Acceptance test framework will be established soon.
> The proposal is to assert the project is OK basically. we don't expect it
> can
Acceptance test framework will be established soon.
The proposal is to assert the project is OK basically. we don't expect it
can assert all function details.
We prefer using uint tests and integrated test engine to assert all
function details, it is fine now.
So, IMO, we can establish the
It looks good to me, but it’s better we have a mechanism to verify whether
4.0.0 is stable or not.
--
Zhao Jun (cherrylzhao)
Apache Sharding-Sphere & ServiceComb
> On Dec 9, 2019, at 10:53 AM, Sheng Wu wrote:
>
> zhaojun 于2019年12月9日周一 上午10:21写道：
>
>> @Sheng
>>
>> Maybe you
zhaojun 于2019年12月9日周一 上午10:21写道：
> @Sheng
>
> Maybe you have misunderstood what i have said.
> I meant if we have not an acceptance-test framework, maybe we will spend
> another several months to process release work.
> This is a critical problems we should face with.
>
No very critical I think
Finishing Acceptance-test framework is better, but not a block, IMO. As Liang
said, a detailed schedule is necessary to makes everyone review all the tasks
and their time costs.
Juan Pan
panj...@apache.org
Juan Pan(Trista), Apache ShardingSphere
On 12/8/2019 22:50，Sheng Wu wrote：
zhaojun
zhaojun 于2019年12月8日周日 下午9:50写道：
> Acceptance-test framework will make release workflow more smoothly.
> We will spend a lot of time (maybe months) to verify the function manually
> on every release time.
>
Several months? Are you saying ShardingSphere will have no stable release
in over 1.5
Acceptance-test framework will make release workflow more smoothly.
We will spend a lot of time (maybe months) to verify the function manually on
every release time.
In fact, we could not release a version ASAP now.
--
Zhao Jun (cherrylzhao)
Apache ShardingSphere & ServiceComb
>
14 matches
Mail list logo
