Hi contributors, Happy holiday for Chinese developers! Here are updates among TiDB projects in the last two weeks. Overall it consists of three parts, TiDB developments, notable bugs and events, blog

Hi contributors, Now the dependency cleanup phase of the Standalone Go Client project[1] is coming to an end, which means that store/tikv will soon stop importing other packages of tidb. The next step

Hi contributors, Open source projects always benefit from "the bazaar" developing mode, which means we contributors are free to read the code, ask questions, and "kaisen"(improve) the software as indi

Hi contributors, As mentioned in the previous email, we TiDB contributors already have two open communication way, said Slack and mailing list. However, neither works very well from my perspective. In

Hi contributors, I've just turned on the CI of pingcap/errors[1]. It doesn't touch any production code but now we can verify fix by adding tests and prevent regression from travis ci. Please help on r

Hi contributors, Last week there were quite a few development tasks kicked off, so this mail contains most of the development tasks. Overall it consists of three parts, TiDB developments, notable bugs

In February 2018, the former TiDB team started a series of blogs about TiDB source code reading to reveal the implementation internals of TiDB, which is on the source-code branch of the tidb repo. The

Hello, we are now beginning to develop the CTE(common table expression). CTE is introduced in SQL:1999. It's a temporary result set that exists within a statement. You can reference it later in the st

Hi contributors, At Monday(04.19) we have a meeting on foreign data access design. And I'd like to share you about the progress made at the moment. First of all is the design document[1], which is Chi

Hi contributors, Recently I dropped two survey letters[1][2] on our mailing list and get quite a few feedbacks. It seems mailing list is still loved by a number of our contributors[3][4]. Given that i

As the operations manager of the TiDB Community, I would recommend the mailing list. From the perspective of community operations, we prefer tools that can accumulated. For example, a new Contributor

Dear Contributors, We will host an Infra Meetup on April 10th in Beijing. It's the first offline event of the TiDB Community since the COVID-19 epidemic. With the continuous development of the TiDB co

Dear Contributors, For the past while, we've used ti-srebot to help the TiDB community collaborate on GitHub. But the robot no longer met our requirements due to missing documentation and some design

Dear Contributors, Recently an exciting feature, named Coprocessor Plugin, to TiKV has been under proposal and experimental implementation. The motivation is to support executing arbitrary user-define

Dear Contributors, We are preparing and planning to develop some new collaboration infrastructure tools, and we have used RFCs to describe the features and design of each tool. If you are interested i

Dear Contributor, At the just concluded TiDB Hackathon 2020, developers across the world did a lot of amazing work on solutions to improve the productivity and efficiency of TiDB and its ecosystem pro

Dear Contributor, In the past we used PR for SIG promotion nominations in the community repository, and used bots for automatic data updates and maintenance. However, many problems were found in the p

Dear Contributor, The TiDB Community is excited to introduce the TiDB Incubator Program, a program designed to ensure that new projects in the TiDB ecosystem can obtain resources and help from the com

The First Meeting of BigData SIG When: Monday, 25 January 2021 5:00pm to 6:00pm (GMT+08:00) Asia/Chongqing Where: Meeting Zoom: https://pingcap.zoom.com.cn/j/8573700836 Description: BigData SIG covers

Dear Contributor, The BigData SIG has established. BigData SIG covers the areas where TiDB and big data are combined, including but not limited to TiDB + Flink, TiDB + Spark, TiDB + Presto. Anyone who