Hi Seata Community, I am writing to provide you with the minutes from our community meeting held on January ６, 202４. The meeting was productive, and we covered several important topics and conclusion as outlined below:
Moderator: Zhengtao Zhong *Attendees* (PPMC only, others refer to the appendix): Min Ji, Te Wang, Liang Wang, Jianbin Chen, Zhengtao Zhong, Jiawei Zhang, Yuecai Liu, Jiangke Wu, etc., totaling 14 people. *Minutes of the Meeting in Chinese：* https://github.com/apache/incubator-seata/wiki/20240106 *Discussion items:* 1. Collect contributor information traceability that exceeds 100 lines of contribution - Add information about other repo, remark not found email contributor. 2. Signed by ASF ICLA contributor - After relocating the repo, contact the corresponding developer via email - review email template 3. Home Compliance & Security - Default language has been changed to English completed - The official website has added license check, dependency check, license and url updates completed - Commercial links have been removed - Maintainer list removed - Official website security vulnerability repaired - User registration removal - logo transformation - English blog. just translate existing ones - seata 41 front-end security vulnerabilities - seata go has 5 vulnerabilities remaining - seata simple 125 remaining - Compliance related issues. https://github.com/apache/incubator-seata/discussions/6233 4. Baidu search traffic decline problem - CI automatically generates sitemap.xml and site.txt completed - Content pre-rendering transformation has been completed - The API automatic reporting function to Baidu has been completed, but the quota given by Baidu is very small - Official website keyword optimization - Improve page experience score 5. Abandon Yuque; historical documents moved to wiki - Scattered documents are not migrated completed - Documents such as design and extracurricular materials need to be migrated completed - Create a new directory for storage completed - Migrate summercode related documents to the corresponding directory 6. 1.8.0 + 2.0.0 documentation, releaseNotes, samples updated - 1.8.0 + 2.0.0 releaseNotes completed - java sample(No new version has been released yet, no need to upgrade yet), seata version upgraded to 2.0, Public logic optimization. 7. Branch maintenance. Maintenance Plan Public Documentation - Maintain according to versions, only maintain the latest 3 versions (wait feedback) 8. Compatibility scheme. Combing API - User api combing, saga completed - State Machine Designer Framework Selection and Basic Framework - Log format input 9. Single test coverage target - Divide different subtasks - Spring autoconfigure is finished, wait merge. - Inaccurate coverage calculation problem - Change coverage needs to be maintained at 70% - Sorting out current module coverage documents - Standards for writing unit tests 10. Building testing and regression capabilities - summer code e2e integration testing framework, wait feedback - Substantially identical codes are not allowed - Run integration tests afterwards (independent repo) - redis needs to test version compatibility - Confirm the collective test plan/standard first 11. Compatibility testing (jdk, arch, spring core+boot, druid) - os, jdk, spring boot, compatibility test pr, completed - Separate workflows to improve parallelism - Test the mysql driver version; test the compatibility of different versions of workflow; 12. Performance benchmark - Only test framework consumption, sql logic - Open source stress testing tools assist in establishing benchmarks - Contains graphics (To be determined) - Determine to add new module implementation - Performance benchmark issues 13. mock test - A preliminary review has been completed. A separate PR will be submitted for mock-server next week, and seata-samples will be mentioned in some content. - Add test case 14. Backlog PR disposal - java: No one has followed up before May 2022, and has been closed, and messages have been left, except for some important ones (completed) - go: Some parts have been contacted by the author (Review will be restarted recently, and the merged version will be merged) - PRs that take too long and PRs that cannot be contacted (important and needed) will be followed up by us 15. Support spring boot actuator - Complete redis - Need to keep health check - connection pool 16. Package migration org.apache.seata - The current PR will be merged as soon as possible and processed uniformly; 17. resource id + application name Uniquely identifies - The resource id may be duplicated, causing distribution problems. To ensure uniqueness, the final plan is tentative and the meeting will be held again for discussion. - Communicate and prepare documents at the next meeting; requirements can be dynamically expanded; 18. tcc usage confirmation, whether it needs to be compatible with special usage methods - Unified specifications: The java tcc annotation standard is unified and applied to the implementation class. After the rm is completed, it needs to be disclosed in the document. In addition, the LocalTcc annotation is discarded and the TwoPhase annotation is also used; - As a reminder on how to use tcc annotations, if the second-stage annotation is printed on the interface, the default behavior is: supported rpc framework, prompting warning; unsupported rpc framework, direct exception, the above behavior can be controlled according to the same switch, the judgment is Is there a warning log prompt or an exception prompt? 19. seata go goal - Compliance governance: management of warehouses, some dependent packages, CVE vulnerability repair - Construction and implementation of seata go saga framework - Align the features and bugfixes of seata java. The current one is version 1.5.1, which needs to be upgraded. - Ecological expansion: Service frameworks such as Bilibili 20. Typesetting issues in public accounts - https://github.com/seata/seata/wiki/Wechat 21. token automatically refreshes - https://github.com/apache/incubator-seata/discussions/6180 22. Integrated RocketMQ task claiming - The topic of SummerCode2021 has been basically implemented by students who have submitted a PR. The PR has not been merged and needs to be integrated into the 2.x branch. It is planned to be released in version 2.1.0 23. RocketMQ integration solution - Option 1: Only proxy transaction messages (sendMessageInTransaction), which is more in line with the user's behavioral intentions; - Option 2: All messages are proxied, and the consistency is better, but it may not necessarily meet the user's original intention. - Option 3: Provide manual API calls - Other better solutions? 24. used by retention plan discussion - https://github.com/apache/incubator-seata/discussions/6058 25. TYPE_SEATA_MERGE messages require independent thread pool processing - https://github.com/apache/incubator-seata/issues/6197 26. RM/proxy init startup sequence problem - Conclusion: TM/RM is not init, rm is registered, no longer ignored, direct exception; 27. Jackson is a strong dependency and scope-provided is modified into compile dependency. 28. Issue claim - https://github.com/apache/incubator-seata/issues/6191 - https://github.com/apache/incubator-seata/issues/6189 - https://github.com/apache/incubator-seata/issues/5454 - https://github.com/apache/incubator-seata/issues/5043 - https://github.com/apache/incubator-seata/issues/5136 - https://github.com/apache/incubator-seata/issues/5631 - https://github.com/apache/incubator-seata/issues/5359 - https://github.com/apache/incubator-seata/issues/3752 29. PR Review - https://github.com/apache/incubator-seata/pull/6004 - https://github.com/apache/incubator-seata/pull/5399 - https://github.com/apache/incubator-seata/pull/6169 - https://github.com/apache/incubator-seata/pull/6017 - https://github.com/apache/incubator-seata/pull/5300 Best regards, Zhengtao Zhong
