Re: IoTDB Logo Design

2019-03-10 Thread Xiangdong Huang
+1! I have been looking forward to it for a long time. :P Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Stefanie Zhao 于2019年3月11日周一 上午11:21写道： > > Sorry, the direct link is dropped by the email engine. The jira link is: >

Re:IoTDB Logo Design

2019-03-10 Thread Stefanie Zhao
Sorry, the direct link is dropped by the email engine. The jira link is: https://issues.apache.org/jira/browse/IOTDB-42. -- 赵馨逸 清华大学软件学院 信息系统与工程研究所 Xinyi Zhao(Stefanie) School of Software, Tsinghua University E-mail:stefanie_...@163.com At 2019-03-11 11:07:33, "Stefanie Zhao" wrote: >Dear

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Christofer Dutz
Ah ... oh .. ok .. yeah ... you are right ;-) Sorry for the confusion. Chris Am 10.03.19, 10:57 schrieb "Julian Feinauer" : Hi Chris, I think there is slight confusion. Currently iotdb has no develop and only master branch where development happens. Thus I suggest to create

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Christofer Dutz
Hi all, So I just did a first "mvn clan install -P apache-release" as a test for what a maven release would produce. - Unfortunately I got two test-failures: IoTDBDeletionIT.test IoTDBDeletionIT.testMerge After disabling those two tests the build passed. Then I had a look at the build

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Xiangdong Huang
This document is clear. Actually now our master branch play the actor of the "develop" branch in the document. As the document says, "The *master branch* tracks released code only. The only commits to *master* are merges from *release branches* and *hotfix branches*." Then the responsibility of

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread ???? Sheng Wu
> But I find that it seems the branch does not have effect... Normally, If a PR pass all CI test (if the CI test is enough complete), then if we merge it into the master, we can guarantee the master is also stable This is how the dev branch work. CI can guarantee the stable just in theory.

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Xiangdong Huang
Hi, Agree. I once wanted to maintain a branch called `dev`, so we can submit PRs to the `dev` branch, and then merge `dev` into `master`.. (actually `dev` branch exists on github repo now...) But I find that it seems the branch does not have effect... Normally, If a PR pass all CI test (if the

Refactor Overflow module

2019-03-10 Thread Xiangdong Huang
Hi, When I refactor the filenode module, I found that Overflow module needs to be refactor first.. Overflow is similar with BufferWrite (sequence memtable), but it will generate OverflowFiles which is similar with TsFile but has some different properties... (for handling out-of-order data). I

AW: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Julian Feinauer
Hi Chris, I think there is slight confusion. Currently iotdb has no develop and only master branch where development happens. Thus I suggest to create the file there (as done in my PR #91). Julian Von meinem Mobiltelefon gesendet Urspr??ngliche Nachricht Betreff: Re: Do we

Re: Do we have a plan to release the first normal version of IoTDB this month?

2019-03-10 Thread Christofer Dutz
In other projects, we usually have release notes also in develop. Here we have a section for the next planned version right at the top (but with an "unreleased" appended to the version) and add stuff as it comes in. For a release the "unreleased" is removed and merged to master, then a new