Sorry, when the translation content is too long, I am not sure whether the translation software can understand what I want to say.
In general, the project is gradually attracting people who really pay attention and use it, and the project will be adjusted from next month. Thanks! Goson zhang <[email protected]> 于2021年5月28日周五 下午4:12写道： > Hello everyone: > > Summarize the recent situation: > 1. Branch 570: now it has entered the testing phase, after this content is > launched, the readability and scalability of Web APIs and metadata > management will be more better, which is convenient for subsequent feature > expansion; due to the compatibility of previous versions, the old version > of the API and the underlying BDB data storage classes are still retained, > although these old APIs and storage formats are somewhat obsolete; > > 2. Branch 25: pure Go language SDK, compared with the previous stage, the > contributors of this module have already started actual code contributions. > If you are interested in Go language implementation and want to > participate, you can pay attention to its issue. > > 3. The main body of InLong will start to move next month: thanks mentor > @Justin, > @JB have prepared the basic environment of the project. Everyone may pay > attention that InLong's code and website content have not been adjusted > according to the name change (maybe the people involved in this project are > asleep), and someone who chooses to contribute to this problem. First of > all, thank contributors @RocMarshal and @leven-space for finding this > problem and Initiated an improvement; considering that the changes are too > large, we will release it when we are ready, and track the content of each > improvement through INLONG-613 and INLONG-614, until all the content is > prepared on the branch, and then merged into the project master. > > 4. A code contribution Tips：when we contribute, we must consider the issue > of originality and respect for originality, when we contribute code, if we > directly quote external code, we need to declare in the LICENSE and NOTICE > of the project, which files are quoted from where, or else it will form > infringement; as we directly quote external codes, the LICENSE and NOTICE > of the ontology project will expand, this result will make people feel that > the project is a hodgepodge. TubeMQ did not consider this issue at first, > now we will reduce the direct quotation of the source code of external > projects, so we should be as original as possible when contributing code. > > The last, after the metadata management transformation is completed, in > addition to switching the BDB storage module, we will also renovate some > old implementations. If you see some bad implementations, please feel free > to contribute. > > Thanks all! > > > ---------- Forwarded message --------- > 发件人： Goson zhang <[email protected]> > Date: 2021年4月30日周五 上午9:46 > Subject: [Monthly report -- 20210430] Project progress feedback > To: <[email protected]> > > > Hello everyone: > > > Recent project progress: > 1. Branch 570 has completed the refactoring of the Web APIs: about 80 APIs > have been adjusted according to the new plan, next, the application logic > MetaDataManager class of metadata will be adjusted. After adjustments are > finished, the tests will be performed, including unit tests, integration > test, compatibility test, and verification are passed, and then the > document is written, finally merged into the main branch. After the main > line branch is merged, the development branch of the metadata removal BDB > component will be started. > > 2. The SDK of pure Go language has also been assigned(INLONG-25): A man > who is concerned about the project and willing to contribute to our project > has done an analysis and started the code implementation. The charm of the > open source community is that it is as if a seed has been planted, and it > begins to sprout and grow without knowing it. > > 3. The InLong project is slowly gathering resources, and an initial > version will be released as soon as possible: since rename took nearly 4 > months from the time the application was filed to the final implementation, > which was far more than expected, so, the resources gathered in the early > stage, need to gradually join in, but don't worry, things are changing. > > By the way, I saw that the latest version of Kafka has removed the > zookeeper, great! TubeMQ has removed zookeeper from the core logic around > 2017. But now to comply with Apache's LICENSE specification, we will also > consider supporting metadata storage components including Zookeeper :). > > That's it, happy May Day, everyone! > > Thanks! > > > ---------- Forwarded message --------- > 发件人： Goson zhang <[email protected]> > Date: 2021年3月24日周三 上午10:57 > Subject: [Monthly report] Project progress feedback > To: <[email protected]> > > > Hello everyone: > > The community of the project has been a bit quiet recently, not everyone > is asleep, we are dealing with the following content: > > 1. The content preparation of the rename project: > According to our previous discussion of renaming, our mentor has submitted > a renaming Jira[1] (thanks to mentor JB), we need to organize the relevant > project content before the implementation of the renaming, including the > new project homepage, Logo, other open source components, etc. > Please wait, it is expected that the overall content of the project will > be updated after the name change is completed at the end of March, or early > April if the rename operation delays. > > 2. Metadata store component transformation: > This part is performing online, refer to the branch TUBEMQ-570. Due to the > license issue of BDB, we need to switch the metadata storage and the > keep-alive mechanism of the system to Zookeeper. Since this part is a > replacement of basic components, there is a transition, which will switch > to zk after the code abstraction is completed. and anyone interested can > pay attention to this branch. > > 3. Development tubemq-manager node: > This part is also carried out online, refer to the branch TUBEMQ-421. The > requirement of this part is to be an independent management node that spans > multiple TubeMQ clusters to facilitate system operation and maintenance. > > As the related changes are relatively large work, we are going to release > the version after the rename of InLong is completed. So, for users of > TubeMQ 0.8.0 version, there is a problem that needs to be paid attention > to, a bug was recently discovered [2], which affects the information query > of webAPI. Before the version is released, please refer to the issue[2] and > fix it self: > > 1. > https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allopenissues > 2. > https://issues.apache.org/jira/projects/TUBEMQ/issues/TUBEMQ-577?filter=doneissues > > If you have any questions, feedback is welcome. > > Thanks all! > > >
