A question, traditionally, the 3rd version number means bug fix, but the changelogs include enhancement. Do we set the 2nd version number for new feature only?
Sheng Wu 吴晟 Twitter, wusheng1108 [email protected] <[email protected]> 于2020年2月9日周日 下午5:34写道： > +1. > Great. There are no missing tasks from my side. > > ------------------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > zhaojun <[email protected]> 于2020年2月9日周日 下午3:44写道： > > > Hi, ShardingSphere community, > > > > I’d like to be the release manager of 4.0.1 version. > > We have done some bug fixes and performance optimization in past month > > based on 4.0.0. > > If there is no other requirement, I think we can start to release 4.0.1 > > recently. > > > > > > ## Bug fixes > > > > 3975 oracle insert SQL could not work in encrypt mode > > 3997 proxy for PostgreSQL decode parameters error in all types except > > String > > 4022 none sharding strategy could not config in spring-boot > > 4052 plain column could not get from resultSet in sharding-encrypt mode > > 4173 wasNull field was wrong in GroupByStreamMergeResult > > > > > > ## Enhancement > > > > 3956 using guava cache to improve parsing performance > > 4004 optimize COM_STM_EXECUTE of MySQL to support sysbench > > 4054 optimize antlr performance using two-stage parsing strategy > > 4205 add class filter constructor to restrict the illegal class from > YAML > > > > Thanks to these contributors for their code commits. > > - tuohai666, xiyelife, SteNicholas, KomachiSion, beckhampu, > plazmdk > > > > Any other task missing here? Please feel free to let me know. > > > > ------------------ > > Zhao Jun (cherrylzhao) > > Apache ShardingSphere & ServiceComb >
