Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > Looks good. I think we need our mentors to confirm that. It’s fine by me. Thanks, Justin
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Looks good. I think we need our mentors to confirm that. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 乔嘉林 Jialin Qiao 于2019年3月14日周四 上午9:54写道： > Hi, Xinyi > > Thank you so much! > > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > -原始邮件- > > 发件人: "Stefanie Zhao" > > 发送时间: 2019-03-14 09:41:31 (星期四) > > 收件人: "[email protected]" > > 抄送: > > 主题: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > > > Hi, Jialin > > > > > > EDL1.0 is Eclipse Distribution License 1.0, under category-a[1]. So we > can use it. > > > > > > [1] http://www.apache.org/legal/resolved.html#category-a > > > > > > Best, > > -- > > Xinyi Zhao(Stefanie) > > School of Software, Tsinghua University > > E-mail:[email protected] > > > > > > > > 在 2019-03-14 09:35:13，"乔嘉林 Jialin Qiao" > 写道： > > >Hi, > > > > > >To support jdk11, we need to add a dependency > "com.sun.istack:istack-commons-runtime:3.0.6", which is under EDL 1.0. > > >However, I can't find EDL 1.0 in any of the ASF 3rd Party > categories[1]. So, can we include this dependency in our binary > distribution? > > > > > >[1] http://www.apache.org/legal/resolved.html#category-a > > > > > >Thanks. > > >-- > > >Jialin Qiao > > >School of Software, Tsinghua University > > > > > >乔嘉林 > > >清华大学 软件学院 >
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Xinyi Thank you so much! -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Stefanie Zhao" > 发送时间: 2019-03-14 09:41:31 (星期四) > 收件人: "[email protected]" > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, Jialin > > > EDL1.0 is Eclipse Distribution License 1.0, under category-a[1]. So we can > use it. > > > [1] http://www.apache.org/legal/resolved.html#category-a > > > Best, > -- > Xinyi Zhao(Stefanie) > School of Software, Tsinghua University > E-mail:[email protected] > > > > 在 2019-03-14 09:35:13，"乔嘉林 Jialin Qiao" 写道： > >Hi, > > > >To support jdk11, we need to add a dependency > >"com.sun.istack:istack-commons-runtime:3.0.6", which is under EDL 1.0. > >However, I can't find EDL 1.0 in any of the ASF 3rd Party categories[1]. > >So, can we include this dependency in our binary distribution? > > > >[1] http://www.apache.org/legal/resolved.html#category-a > > > >Thanks. > >-- > >Jialin Qiao > >School of Software, Tsinghua University > > > >乔嘉林 > >清华大学 软件学院
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Jialin EDL1.0 is Eclipse Distribution License 1.0, under category-a[1]. So we can use it. [1] http://www.apache.org/legal/resolved.html#category-a Best, -- Xinyi Zhao(Stefanie) School of Software, Tsinghua University E-mail:[email protected] 在 2019-03-14 09:35:13，"乔嘉林 Jialin Qiao" 写道： >Hi, > >To support jdk11, we need to add a dependency >"com.sun.istack:istack-commons-runtime:3.0.6", which is under EDL 1.0. >However, I can't find EDL 1.0 in any of the ASF 3rd Party categories[1]. So, >can we include this dependency in our binary distribution? > >[1] http://www.apache.org/legal/resolved.html#category-a > >Thanks. >-- >Jialin Qiao >School of Software, Tsinghua University > >乔嘉林 >清华大学 软件学院
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, To support jdk11, we need to add a dependency "com.sun.istack:istack-commons-runtime:3.0.6", which is under EDL 1.0. However, I can't find EDL 1.0 in any of the ASF 3rd Party categories[1]. So, can we include this dependency in our binary distribution? [1] http://www.apache.org/legal/resolved.html#category-a Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Thanks for your help. Xinyi and I worked together to make a thorough check of our dependencies and license. We found that we had many unneeded dependencies and we removed them. In the source codes, the only files we use are from Apache Hive, under Apache License-2.0. These files are not modified and are declared in the License file: APACHE IOTDB SUBCOMPONENTS: Apache IoTDB project includes a number of submodules with separate copyright notices and license terms. Your use of these submodules is subject to the terms and conditions of the following licenses. Apache Software Foundation License 2.0 -- iotdb/src/main/java/org/apache/iotdb/db/sql/parse/AstErrorNode.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/AstNode.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/AstNodeOrigin.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/Node.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/ParseDriver.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/ParseError.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/ParseException.java iotdb/src/main/java/org/apache/iotdb/db/sql/parse/ParseUtils.java For the binary distribution, softwares that are bundled in the binary distribution are all listed here: (Execute "mvn clean package -DskipTests" and the jars will be found in the iotdb/iotdb/lib/) antlr-runtime-3.5.2.jar commons-collections4-4.0.jar commons-io-2.5.jar commons-lang3-3.8.1.jar fastjson-1.2.31.jar hamcrest-core-1.3.jar junit-4.12.jar libthrift-0.9.3.jar logback-classic-1.1.11.jar logback-core-1.1.11.jar mockito-all-1.10.19.jar slf4j-api-1.7.12.jar snappy-java-1.0.5-M1.jar They're also declared in the License file: The binary distribution of this product bundles these dependencies under the following license. See licenses/ for text of these licenses. Apache Software Foundation License 2.0 -- commons-cli:commons-cli:1.3.1 commons-io:commons-io:2.5 org.apache.commons:commons-collections4:4.0 org.apache.commons:commons-lang3:3.1 org.apache.thrift:libthrift:0.9.3 org.xerial.snappy:snappy-java:1.0.5-M1 com.alibaba:fastjson:1.2.31 BSD 2-Clause jline:jline org.hamcrest:hamcrest-core:1.3 org.hamcrest:hamcrest-library:1.3 BSD 3-Clause org.antlr:antlr-runtime:3.5.2 MIT License --- org.slf4j:slf4j-api org.mockito:mockito-all:1.10.19 EPL 1.0 --- ch.qos.logback:logback-classic:1.1.11 ch.qos.logback:logback-core:1.1.11 EPL 2.0 --- junit:junit:4.12 Now, all licenses will be fine in our project. All modifications are in this PR: https://github.com/apache/incubator-iotdb/pull/94 Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Justin Mclean" > 发送时间: 2019-03-13 16:43:32 (星期三) > 收件人: [email protected] > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > HI, > > > The PLC4X podling uses logback too ... So it should be ok. I think being > > dual licensed, we could choose the license in that particular case. > > Yes I agree, you select the more favourable licence and include that in your > binary LICENSE file. > > Thanks, > Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
HI, > The PLC4X podling uses logback too ... So it should be ok. I think being dual > licensed, we could choose the license in that particular case. Yes I agree, you select the more favourable licence and include that in your binary LICENSE file. Thanks, Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
The PLC4X podling uses logback too ... So it should be ok. I think being dual licensed, we could choose the license in that particular case. Chris Outlook für Android<https://aka.ms/ghei36> herunterladen From: 乔嘉林 Jialin Qiao Sent: Wednesday, March 13, 2019 9:22:02 AM To: [email protected] Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Currently, we use logback as the implementation of slf4j log framwork, so it is included in our binary distribution. Link to logback: https://mvnrepository.com/artifact/ch.qos.logback/logback-classic However, logback has two license: EPL 1.0, LGPL 2.1. EPL 1.0 is allowed in the binary distribution, but LGPL 2.1 can't be included. In this case, can we use logback as a dependency? Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Currently, we use logback as the implementation of slf4j log framwork, so it is included in our binary distribution. Link to logback: https://mvnrepository.com/artifact/ch.qos.logback/logback-classic However, logback has two license: EPL 1.0, LGPL 2.1. EPL 1.0 is allowed in the binary distribution, but LGPL 2.1 can't be included. In this case, can we use logback as a dependency? Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi jialin, Do not just modify the LICENSE and NOTICE file. What you need is tell us why you remove/replace something (maybe not only the JSON). You may need to post a list: License name, which jars that use it, action( remove/replace), how source codes are modified. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 乔嘉林 Jialin Qiao 于2019年3月13日周三 上午11:08写道： > Hi, > > Forgot to say, it is org.json that is JSON licensed. > > Thanks. > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > -原始邮件- > > 发件人: "Justin Mclean" > > 发送时间: 2019-03-13 09:15:26 (星期三) > > 收件人: [email protected] > > 抄送: > > 主题: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > > > Hi, > > > > Looking through the code I can see this a couple of times: > > import org.json.JSONArray; > > import org.json.JSONObject; > > > > And those the dependancies that are JSON licensed? > > > > Could these be replace with something under a more friendly and > compatible license i.e. Jackson? > > > > Thanks, > > Justin >
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Forgot to say, it is org.json that is JSON licensed. Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Justin Mclean" > 发送时间: 2019-03-13 09:15:26 (星期三) > 收件人: [email protected] > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, > > Looking through the code I can see this a couple of times: > import org.json.JSONArray; > import org.json.JSONObject; > > And those the dependancies that are JSON licensed? > > Could these be replace with something under a more friendly and compatible > license i.e. Jackson? > > Thanks, > Justin
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I replaced all org.json by com.alibaba.fastjson in our project in the same PR, which is under Apache License-2.0. The link is: https://github.com/apache/incubator-iotdb/pull/94 Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Justin Mclean" > 发送时间: 2019-03-13 09:15:26 (星期三) > 收件人: [email protected] > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, > > Looking through the code I can see this a couple of times: > import org.json.JSONArray; > import org.json.JSONObject; > > And those the dependancies that are JSON licensed? > > Could these be replace with something under a more friendly and compatible > license i.e. Jackson? > > Thanks, > Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Looking through the code I can see this a couple of times: import org.json.JSONArray; import org.json.JSONObject; And those the dependancies that are JSON licensed? Could these be replace with something under a more friendly and compatible license i.e. Jackson? Thanks, Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > I have removed the JSON license in this PR: > https://github.com/apache/incubator-iotdb/pull/94 I’m a little confused. I can see this PR just removes the license file. But I assume there was a reason the license in there in the first place? I assume that something is licensed in that way, if so what was that? Thanks, Justin
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I have removed the JSON license in this PR: https://github.com/apache/incubator-iotdb/pull/94 Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Justin Mclean" > 发送时间: 2019-03-13 05:44:11 (星期三) > 收件人: [email protected] > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, > > > Now you may need to include what in Hive NOTICE file in your NOTICE file. > > Looking at it [2] I’m horrified to find "This project includes software > > licensed under the JSON license.” which is a category X and can’t be > > included in an ASF project. > > I emailed the Hive project and that line is in their NOTICE by mistake, they > removed the JSON code some time back but didn’t update their NOTICE. > > Thanks, > Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
It means the maven wrapper[1] not the maven version. There is MavenWrapperDownloader.java file in the .mvn/wrapper need to be updated. Please use the latest version for it. [1]https://github.com/takari/maven-wrapper Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: > > Hi, > > > As you mentioned "The maven-wrapper should be updated to the latest version", > but I did not find anything related to maven wrapper version? > > > Thanks > XuYi > On 3/11/2019 02:31，Christofer Dutz wrote： > 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 results. I did notice that the pom doesn't > have an asc (signature), but the sha512 look ok. > > - The LICANSE file contains invalid paths ... > ql/src/java/org/apache/hadoop/hive/ql/ > These don't exist, but seem to have to be changed to: > iotdb/src/java/org/apache/hadoop/hive/ql/ > However these files don't seem to exist at all: > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java > > - Why is there two LICENSE files? This is quite unusual. > > - The binary version references libraries that seem to be referenced by the > build: > joda-time:joda-time > org.apache.maven.wagon:wagon-provider-api > org.apache.maven:maven-artifact > org.apache.maven:maven-artifact-manager > org.apache.maven:maven-model > org.apache.maven:maven-plugin-api > org.apache.maven:maven-profile > org.apache.maven:maven-project > org.apache.maven:Maven-repository-metadata > org.apache.thrift:Libthrift (should be lower-case libthrift) > org.codehaus.plexus:plexus-compiler-api > org.codehaus.plexus:plexus-container-default > org.codehaus.plexus:plexus-utils > org.antlr:antlr > org.antlr:ST4 > org.antlr:antlr3-maven-plugin > > Guess usually these are dependencies seem to be used by the Maven build and > not the built software. This usually isn't mentioned in LICENSE files. > > - If org.hamcrest:hamcrest-core is mentioned, so should > org.hamcrest:hamcrest-library > > - Then sometimes multiple different versions of one library are used, which > is not desirable. > > - Why are there two versions of NOTICE files (Haven't checked the content as > it was quite excessive) > > - There doesn't seem to be a RELEASE_NOTES file > > - The maven-wrapper should be updated to the latest version as that version > invalidly contained an Apache header which suggests it's an Apache Software. > This has been brought up in the incubator list and will probably be mentioned > in the future. > Please just update the source files with the latest versions of the > maven-wrapper library. > > So ... now I'll got back to my skiing holidays. Just thought I'd report that > ... not sure if these findings are release-breakers, however it might be a > good idea to address and/or discuss them soon. > > Chris > > > Am 10.03.19, 10:42 schrieb "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 entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > From: 吴晟 Sheng Wu > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may be > interesting in the changes of old versions, in order to choose right version. > And, make sense to create a new branch to do release, and versiob update. You > could make the version to 0.9.0-snapshot, after the release branch created. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: Xiangdong Huang > Date: Sun,Mar 10,2019 11:48 AM > To: dev > Subject: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > > &g
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > Now you may need to include what in Hive NOTICE file in your NOTICE file. > Looking at it [2] I’m horrified to find "This project includes software > licensed under the JSON license.” which is a category X and can’t be included > in an ASF project. I emailed the Hive project and that line is in their NOTICE by mistake, they removed the JSON code some time back but didn’t update their NOTICE. Thanks, Justin
Re: Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I misunderstood. Both files are ASF files and no modifications are made. Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Xiangdong Huang" > 发送时间: 2019-03-12 19:17:17 (星期二) > 收件人: [email protected] > 抄送: > 主题: Re: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > Hi, > > I think what Justin concerns are (1) does the files you copy/modify are > also ASF projects or under Apache License 2.0? (the answer is yes.) (2) > What modifications (except for the header content) you have made on these > files? > > I do not know whether we need to add "Based on ASTNode.java from Apache > Hive" to our related files. But if we just use ASTNode from Apache Hive, I > think no codes rely on JSON license. (at least this part of Hive should not > be licensed by JSON license, I think). > > And we can find the conflict licenses here (Category X): > https://www.apache.org/legal/resolved.html#category-x > We need to replace theses dependencies. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > 乔嘉林 Jialin Qiao 于2019年3月12日周二 下午5:24写道： > > > > > Hi, > > > > These files are all in the IoTDB project, under > > "iotdb/src/main/java/org/apache/iotdb/db/sql/parse" folder. > > > > Their original headers are: > > > > /** > > * Licensed to the Apache Software Foundation (ASF) under one > > * or more contributor license agreements. See the NOTICE file > > * distributed with this work for additional information > > * regarding copyright ownership. The ASF licenses this file > > * to you under the Apache License, Version 2.0 (the > > * "License"); you may not use this file except in compliance > > * with the License. You may obtain a copy of the License at > > * > > * http://www.apache.org/licenses/LICENSE-2.0 > > * > > * Unless required by applicable law or agreed to in writing, > > * software distributed under the License is distributed on an > > * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > > * KIND, either express or implied. See the License for the > > * specific language governing permissions and limitations > > * under the License. > > */ > > > > These files are based on some classes from Apache Hive, which also use > > Apache License-2.0. > > So the following is newly added below the origin header in this PR. > > Maybe it's not needed... > > > > /** > > * Based on ASTNode.java from Apache Hive > > * > > * Licensed to the Apache Software Foundation (ASF) under one > > * or more contributor license agreements. See the NOTICE file > > * distributed with this work for additional information > > * regarding copyright ownership. The ASF licenses this file > > * to you under the Apache License, Version 2.0 (the > > * "License"); you may not use this file except in compliance > > * with the License. You may obtain a copy of the License at > > * > > * http://www.apache.org/licenses/LICENSE-2.0 > > * > > * Unless required by applicable law or agreed to in writing, software > > * distributed under the License is distributed on an "AS IS" BASIS, > > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > > * See the License for the specific language governing permissions and > > * limitations under the License. > > */ > > > > Thanks. > > > > -- > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > > > > -原始邮件- > > > 发件人: "Justin Mclean" > > > 发送时间: 2019-03-12 16:53:16 (星期二) > > > 收件人: [email protected] > > > 抄送: > > > 主题: Re: Do we have a plan to release the first normal version of IoTDB > > this month? > > > > > > Hi, > > > > > > Which tells me nothing sorry. In order to suggest what to do I need to > > know the IP provenance of the file and what changes have been made to it. I > > f that are both actually ASF files and not from anywhere else then that > > make things simple. In general you should almost never replace 3rd party > > headers or add ASF headers to them without that 3rd parties permission. > > > > > > Thanks, > > > Justin > >
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I think what Justin concerns are (1) does the files you copy/modify are also ASF projects or under Apache License 2.0? (the answer is yes.) (2) What modifications (except for the header content) you have made on these files? I do not know whether we need to add "Based on ASTNode.java from Apache Hive" to our related files. But if we just use ASTNode from Apache Hive, I think no codes rely on JSON license. (at least this part of Hive should not be licensed by JSON license, I think). And we can find the conflict licenses here (Category X): https://www.apache.org/legal/resolved.html#category-x We need to replace theses dependencies. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 乔嘉林 Jialin Qiao 于2019年3月12日周二 下午5:24写道： > > Hi, > > These files are all in the IoTDB project, under > "iotdb/src/main/java/org/apache/iotdb/db/sql/parse" folder. > > Their original headers are: > > /** > * Licensed to the Apache Software Foundation (ASF) under one > * or more contributor license agreements. See the NOTICE file > * distributed with this work for additional information > * regarding copyright ownership. The ASF licenses this file > * to you under the Apache License, Version 2.0 (the > * "License"); you may not use this file except in compliance > * with the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, > * software distributed under the License is distributed on an > * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > * KIND, either express or implied. See the License for the > * specific language governing permissions and limitations > * under the License. > */ > > These files are based on some classes from Apache Hive, which also use > Apache License-2.0. > So the following is newly added below the origin header in this PR. > Maybe it's not needed... > > /** > * Based on ASTNode.java from Apache Hive > * > * Licensed to the Apache Software Foundation (ASF) under one > * or more contributor license agreements. See the NOTICE file > * distributed with this work for additional information > * regarding copyright ownership. The ASF licenses this file > * to you under the Apache License, Version 2.0 (the > * "License"); you may not use this file except in compliance > * with the License. You may obtain a copy of the License at > * > * http://www.apache.org/licenses/LICENSE-2.0 > * > * Unless required by applicable law or agreed to in writing, software > * distributed under the License is distributed on an "AS IS" BASIS, > * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > * See the License for the specific language governing permissions and > * limitations under the License. > */ > > Thanks. > > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > -原始邮件- > > 发件人: "Justin Mclean" > > 发送时间: 2019-03-12 16:53:16 (星期二) > > 收件人: [email protected] > > 抄送: > > 主题: Re: Do we have a plan to release the first normal version of IoTDB > this month? > > > > Hi, > > > > Which tells me nothing sorry. In order to suggest what to do I need to > know the IP provenance of the file and what changes have been made to it. I > f that are both actually ASF files and not from anywhere else then that > make things simple. In general you should almost never replace 3rd party > headers or add ASF headers to them without that 3rd parties permission. > > > > Thanks, > > Justin >
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, These files are all in the IoTDB project, under "iotdb/src/main/java/org/apache/iotdb/db/sql/parse" folder. Their original headers are: /** * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, * software distributed under the License is distributed on an * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY * KIND, either express or implied. See the License for the * specific language governing permissions and limitations * under the License. */ These files are based on some classes from Apache Hive, which also use Apache License-2.0. So the following is newly added below the origin header in this PR. Maybe it's not needed... /** * Based on ASTNode.java from Apache Hive * * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Justin Mclean" > 发送时间: 2019-03-12 16:53:16 (星期二) > 收件人: [email protected] > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, > > Which tells me nothing sorry. In order to suggest what to do I need to know > the IP provenance of the file and what changes have been made to it. I f that > are both actually ASF files and not from anywhere else then that make things > simple. In general you should almost never replace 3rd party headers or add > ASF headers to them without that 3rd parties permission. > > Thanks, > Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Soi I’m not sure what is actually in the release but she immediate concerns are: 1, ./licenses-binary/GNU Lesser General Public License version 2.1(LGPL-2.1) LGPL is Category X and can’t be included or be a dependancy of ASLv2 licensed software. 2. ./licenses-binary/The JSON License The JSON license is Category X and can’t be included or be a dependancy of ASLv2 licensed software. 3. ./licenses-binary/Eclipse Public License 1.0 (EPL-1.0) ./licenses-binary/Eclipse Public License version 2.0 (EPL-2.0) These are Category B licenses and can’t be included in a source release. Thanks, Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Which tells me nothing sorry. In order to suggest what to do I need to know the IP provenance of the file and what changes have been made to it. I f that are both actually ASF files and not from anywhere else then that make things simple. In general you should almost never replace 3rd party headers or add ASF headers to them without that 3rd parties permission. Thanks, Justin
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > Take care in copying what TLP project do (especially Spark) as it may be > incorrect or out of date. What changes have been made to that file? In > general significant changes need to have been made in order for the header to > change. [1] Ask yourself is the statement "Licensed to the Apache Software > Foundation (ASF) under one or more contributor license agreements.” actually > true for that file? In the PR, the new file header is: /** * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, * software distributed under the License is distributed on an * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY * KIND, either express or implied. See the License for the * specific language governing permissions and limitations * under the License. */ /** * Based on ASTErrorNode.java from Apache Hive * * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * "License"); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ Are the second paragraph and the "Based on ASTErrorNode.java from Apache Hive" needed? If not, I will remove them. Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > I also added the license in Apache Hive to the class header with a notice > "Based on *.java from Apache Hive", just as Spark does in > > https://github.com/apache/spark/blob/master/common/network-common/src/main/java/org/apache/spark/network/util/LimitedInputStream.java Take care in copying what TLP project do (especially Spark) as it may be incorrect or out of date. What changes have been made to that file? In general significant changes need to have been made in order for the header to change. [1] Ask yourself is the statement "Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements.” actually true for that file? Now you may need to include what in Hive NOTICE file in your NOTICE file. Looking at it [2] I’m horrified to find "This project includes software licensed under the JSON license.” which is a category X and can’t be included in an ASF project. > These are some dependencies seem to be used by the Maven build and not the > built software. This usually isn't mentioned in LICENSE files. > > I have removed these references in the license file. Correct only software bundled in the release needs to be mentioned, dependancies should not be mentioned in LICENSE. Thanks, Justin 1. https://www.apache.org/legal/src-headers.html#3party 2. https://github.com/apache/hive/blob/master/NOTICE
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I have upgraded to 3.6.0 at [1] along with Jialin's pull request. [1] https://github.com/apache/incubator-iotdb/pull/94/files#diff-de2bfeb3d4c0f4a0b3af8d261a26a21a Thanks XuYi On 3/12/2019 15:52，Jiaye Wu wrote： Yeah, I think so. Unless writing a web crawler to fetch the latest version. p.s. In Maven, there is no solution to automatically use the latest version of dependencies. I think it is designed for the sake of reproducible builds. Correct me if I am not right. Thanks, Jiaye On Tue, Mar 12, 2019 at 3:44 PM 徐毅 wrote: Hi So when Maven releases a new version, we should catch up in our maven wrapper file? Thanks XuYi On 3/12/2019 15:41，Jiaye Wu wrote： Hi, You can access this url https://repo1.maven.org/maven2/org/apache/maven/apache-maven/ The latest version is 3.6.0. Thanks, Jiaye On Tue, Mar 12, 2019 at 3:40 PM 徐毅 wrote: Hi, The url is https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip . Should we upgrade to maven 3.5.2 or which version should we upgrade to? Thanks XuYi On 3/12/2019 15:37，Jiaye Wu wrote： Hi Xuyi, Do you refer to the version in https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties ? Thanks, Jiaye On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: Hi, As you mentioned "The maven-wrapper should be updated to the latest version", but I did not find anything related to maven wrapper version? Thanks XuYi On 3/11/2019 02:31，Christofer Dutz wrote： 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 results. I did notice that the pom doesn't have an asc (signature), but the sha512 look ok. - The LICANSE file contains invalid paths ... ql/src/java/org/apache/hadoop/hive/ql/ These don't exist, but seem to have to be changed to: iotdb/src/java/org/apache/hadoop/hive/ql/ However these files don't seem to exist at all: iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java - Why is there two LICENSE files? This is quite unusual. - The binary version references libraries that seem to be referenced by the build: joda-time:joda-time org.apache.maven.wagon:wagon-provider-api org.apache.maven:maven-artifact org.apache.maven:maven-artifact-manager org.apache.maven:maven-model org.apache.maven:maven-plugin-api org.apache.maven:maven-profile org.apache.maven:maven-project org.apache.maven:Maven-repository-metadata org.apache.thrift:Libthrift (should be lower-case libthrift) org.codehaus.plexus:plexus-compiler-api org.codehaus.plexus:plexus-container-default org.codehaus.plexus:plexus-utils org.antlr:antlr org.antlr:ST4 org.antlr:antlr3-maven-plugin Guess usually these are dependencies seem to be used by the Maven build and not the built software. This usually isn't mentioned in LICENSE files. - If org.hamcrest:hamcrest-core is mentioned, so should org.hamcrest:hamcrest-library - Then sometimes multiple different versions of one library are used, which is not desirable. - Why are there two versions of NOTICE files (Haven't checked the content as it was quite excessive) - There doesn't seem to be a RELEASE_NOTES file - The maven-wrapper should be updated to the latest version as that version invalidly contained an Apache header which suggests it's an Apache Software. This has been brought up in the incubator list and will probably be mentioned in the future. Please just update the source files with the latest versions of the maven-wrapper library. So ... now I'll got back to my skiing holidays. Just thought I'd report that ... not sure if these findings are release-breakers, however it might be a good idea to address and/or discuss them soon. Chris Am 10.03.19, 10:42 schrieb "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 entry for the next version is added. Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________ From: 吴晟 Sheng Wu Sent: Sunday, March 10, 2019 4:53:00 AM To: dev; dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You
Re: Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I created a PR to resolve the problems in the license file that Chris mentioned. https://github.com/apache/incubator-iotdb/pull/94 1. The LICANSE file contains invalid paths ... I have updated the paths to current sql parser in IoTDB that we used from Hive. I also added the license in Apache Hive to the class header with a notice "Based on *.java from Apache Hive", just as Spark does in https://github.com/apache/spark/blob/master/common/network-common/src/main/java/org/apache/spark/network/util/LimitedInputStream.java where Spark uses the LimitedInputStream from Google Guava. 2. Why is there two LICENSE files? This is quite unusual. The License-binary is merge with License, and there will be only one license file. 3. The binary version references libraries that seem to be referenced by the build: joda-time:joda-time org.apache.maven.wagon:wagon-provider-api org.apache.maven:maven-artifact org.apache.maven:maven-artifact-manager org.apache.maven:maven-model org.apache.maven:maven-plugin-api org.apache.maven:maven-profile org.apache.maven:maven-project org.apache.maven:Maven-repository-metadata org.apache.thrift:Libthrift (should be lower-case libthrift) org.codehaus.plexus:plexus-compiler-api org.codehaus.plexus:plexus-container-default org.codehaus.plexus:plexus-utils org.antlr:antlr org.antlr:ST4 org.antlr:antlr3-maven-plugin These are some dependencies seem to be used by the Maven build and not the built software. This usually isn't mentioned in LICENSE files. I have removed these references in the license file. 4. If org.hamcrest:hamcrest-core is mentioned, so should org.hamcrest:hamcrest-library This is added. Thanks. -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "徐毅" > 发送时间: 2019-03-12 15:27:18 (星期二) > 收件人: "[email protected]" > 抄送: > 主题: Re: Do we have a plan to release the first normal version of IoTDB this > month? > > Hi, > > > As you mentioned "The maven-wrapper should be updated to the latest version", > but I did not find anything related to maven wrapper version? > > > Thanks > XuYi > On 3/11/2019 02:31，Christofer Dutz wrote： > 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 results. I did notice that the pom doesn't > have an asc (signature), but the sha512 look ok. > > - The LICANSE file contains invalid paths ... > ql/src/java/org/apache/hadoop/hive/ql/ > These don't exist, but seem to have to be changed to: > iotdb/src/java/org/apache/hadoop/hive/ql/ > However these files don't seem to exist at all: > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java > > - Why is there two LICENSE files? This is quite unusual. > > - The binary version references libraries that seem to be referenced by the > build: > joda-time:joda-time > org.apache.maven.wagon:wagon-provider-api > org.apache.maven:maven-artifact > org.apache.maven:maven-artifact-manager > org.apache.maven:maven-model > org.apache.maven:maven-plugin-api > org.apache.maven:maven-profile > org.apache.maven:maven-project > org.apache.maven:Maven-repository-metadata > org.apache.thrift:Libthrift (should be lower-case libthrift) > org.codehaus.plexus:plexus-compiler-api > org.codehaus.plexus:plexus-container-default > org.codehaus.plexus:plexus-utils > org.antlr:antlr > org.antlr:ST4 > org.antlr:antlr3-maven-plugin > > Guess usually these are dependencies seem to be used by the Maven build and > not the built software. This usually isn't mentioned in LICENSE files. > > - If org.hamcrest:hamcrest-core is mentioned, so should > org.hamcrest:hamcrest-library > > - Then sometimes multiple different versions of one library are used, which > is not desirable. > > - Why are there two versions of NOTICE files (Haven't checked the content as > it was quite excessive) > > - There doesn't seem to be a RELEASE_NOTES file > > - The maven-wrapper should be updated to the latest version as that version > invalidly contained an Apache header which suggests it's an Apache Software. > This has been brought up in the incubator list and will probably be mentioned > in the future. > Please just update the source files with the latest versions of the > maven-wrapper library. > > So ... n
Re: Do we have a plan to release the first normal version of IoTDB this month?
Yeah, I think so. Unless writing a web crawler to fetch the latest version. p.s. In Maven, there is no solution to automatically use the latest version of dependencies. I think it is designed for the sake of reproducible builds. Correct me if I am not right. Thanks, Jiaye On Tue, Mar 12, 2019 at 3:44 PM 徐毅 wrote: > Hi > > > So when Maven releases a new version, we should catch up in our maven > wrapper file? > > > Thanks > XuYi > On 3/12/2019 15:41，Jiaye Wu wrote： > Hi, > > You can access this url > https://repo1.maven.org/maven2/org/apache/maven/apache-maven/ > > The latest version is 3.6.0. > > Thanks, > Jiaye > > On Tue, Mar 12, 2019 at 3:40 PM 徐毅 wrote: > > Hi, > > > The url is > > https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip > . > > > Should we upgrade to maven 3.5.2 or which version should we upgrade to? > > > Thanks > XuYi > On 3/12/2019 15:37，Jiaye Wu wrote： > Hi Xuyi, > > Do you refer to the version in > > > https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties > ? > > Thanks, > Jiaye > > On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: > > Hi, > > > As you mentioned "The maven-wrapper should be updated to the latest > version", but I did not find anything related to maven wrapper version? > > > Thanks > XuYi > On 3/11/2019 02:31，Christofer Dutz wrote： > 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 results. I did notice that the pom doesn't > have an asc (signature), but the sha512 look ok. > > - The LICANSE file contains invalid paths ... > ql/src/java/org/apache/hadoop/hive/ql/ > These don't exist, but seem to have to be changed to: > iotdb/src/java/org/apache/hadoop/hive/ql/ > However these files don't seem to exist at all: > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java > > - Why is there two LICENSE files? This is quite unusual. > > - The binary version references libraries that seem to be referenced by > the build: > joda-time:joda-time > org.apache.maven.wagon:wagon-provider-api > org.apache.maven:maven-artifact > org.apache.maven:maven-artifact-manager > org.apache.maven:maven-model > org.apache.maven:maven-plugin-api > org.apache.maven:maven-profile > org.apache.maven:maven-project > org.apache.maven:Maven-repository-metadata > org.apache.thrift:Libthrift (should be lower-case libthrift) > org.codehaus.plexus:plexus-compiler-api > org.codehaus.plexus:plexus-container-default > org.codehaus.plexus:plexus-utils > org.antlr:antlr > org.antlr:ST4 > org.antlr:antlr3-maven-plugin > > Guess usually these are dependencies seem to be used by the Maven build > and not the built software. This usually isn't mentioned in LICENSE files. > > - If org.hamcrest:hamcrest-core is mentioned, so should > org.hamcrest:hamcrest-library > > - Then sometimes multiple different versions of one library are used, > which is not desirable. > > - Why are there two versions of NOTICE files (Haven't checked the content > as it was quite excessive) > > - There doesn't seem to be a RELEASE_NOTES file > > - The maven-wrapper should be updated to the latest version as that > version invalidly contained an Apache header which suggests it's an Apache > Software. This has been brought up in the incubator list and will probably > be mentioned in the future. > Please just update the source files with the latest versions of the > maven-wrapper library. > > So ... now I'll got back to my skiing holidays. Just thought I'd report > that ... not sure if these findings are release-breakers, however it might > be a good idea to address and/or discuss them soon. > > Chris > > > Am 10.03.19, 10:42 schrieb "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 entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunt
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi So when Maven releases a new version, we should catch up in our maven wrapper file? Thanks XuYi On 3/12/2019 15:41，Jiaye Wu wrote： Hi, You can access this url https://repo1.maven.org/maven2/org/apache/maven/apache-maven/ The latest version is 3.6.0. Thanks, Jiaye On Tue, Mar 12, 2019 at 3:40 PM 徐毅 wrote: Hi, The url is https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip . Should we upgrade to maven 3.5.2 or which version should we upgrade to? Thanks XuYi On 3/12/2019 15:37，Jiaye Wu wrote： Hi Xuyi, Do you refer to the version in https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties ? Thanks, Jiaye On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: Hi, As you mentioned "The maven-wrapper should be updated to the latest version", but I did not find anything related to maven wrapper version? Thanks XuYi On 3/11/2019 02:31，Christofer Dutz wrote： 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 results. I did notice that the pom doesn't have an asc (signature), but the sha512 look ok. - The LICANSE file contains invalid paths ... ql/src/java/org/apache/hadoop/hive/ql/ These don't exist, but seem to have to be changed to: iotdb/src/java/org/apache/hadoop/hive/ql/ However these files don't seem to exist at all: iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java - Why is there two LICENSE files? This is quite unusual. - The binary version references libraries that seem to be referenced by the build: joda-time:joda-time org.apache.maven.wagon:wagon-provider-api org.apache.maven:maven-artifact org.apache.maven:maven-artifact-manager org.apache.maven:maven-model org.apache.maven:maven-plugin-api org.apache.maven:maven-profile org.apache.maven:maven-project org.apache.maven:Maven-repository-metadata org.apache.thrift:Libthrift (should be lower-case libthrift) org.codehaus.plexus:plexus-compiler-api org.codehaus.plexus:plexus-container-default org.codehaus.plexus:plexus-utils org.antlr:antlr org.antlr:ST4 org.antlr:antlr3-maven-plugin Guess usually these are dependencies seem to be used by the Maven build and not the built software. This usually isn't mentioned in LICENSE files. - If org.hamcrest:hamcrest-core is mentioned, so should org.hamcrest:hamcrest-library - Then sometimes multiple different versions of one library are used, which is not desirable. - Why are there two versions of NOTICE files (Haven't checked the content as it was quite excessive) - There doesn't seem to be a RELEASE_NOTES file - The maven-wrapper should be updated to the latest version as that version invalidly contained an Apache header which suggests it's an Apache Software. This has been brought up in the incubator list and will probably be mentioned in the future. Please just update the source files with the latest versions of the maven-wrapper library. So ... now I'll got back to my skiing holidays. Just thought I'd report that ... not sure if these findings are release-breakers, however it might be a good idea to address and/or discuss them soon. Chris Am 10.03.19, 10:42 schrieb "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 entry for the next version is added. Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________ From: 吴晟 Sheng Wu Sent: Sunday, March 10, 2019 4:53:00 AM To: dev; dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You could make the version to 0.9.0-snapshot, after the release branch created. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. ------ Original ---------- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:48 AM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the versi
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, You can access this url https://repo1.maven.org/maven2/org/apache/maven/apache-maven/ The latest version is 3.6.0. Thanks, Jiaye On Tue, Mar 12, 2019 at 3:40 PM 徐毅 wrote: > Hi, > > > The url is > https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip > . > > > Should we upgrade to maven 3.5.2 or which version should we upgrade to? > > > Thanks > XuYi > On 3/12/2019 15:37，Jiaye Wu wrote： > Hi Xuyi, > > Do you refer to the version in > > https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties > ? > > Thanks, > Jiaye > > On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: > > Hi, > > > As you mentioned "The maven-wrapper should be updated to the latest > version", but I did not find anything related to maven wrapper version? > > > Thanks > XuYi > On 3/11/2019 02:31，Christofer Dutz wrote： > 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 results. I did notice that the pom doesn't > have an asc (signature), but the sha512 look ok. > > - The LICANSE file contains invalid paths ... > ql/src/java/org/apache/hadoop/hive/ql/ > These don't exist, but seem to have to be changed to: > iotdb/src/java/org/apache/hadoop/hive/ql/ > However these files don't seem to exist at all: > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java > > - Why is there two LICENSE files? This is quite unusual. > > - The binary version references libraries that seem to be referenced by > the build: > joda-time:joda-time > org.apache.maven.wagon:wagon-provider-api > org.apache.maven:maven-artifact > org.apache.maven:maven-artifact-manager > org.apache.maven:maven-model > org.apache.maven:maven-plugin-api > org.apache.maven:maven-profile > org.apache.maven:maven-project > org.apache.maven:Maven-repository-metadata > org.apache.thrift:Libthrift (should be lower-case libthrift) > org.codehaus.plexus:plexus-compiler-api > org.codehaus.plexus:plexus-container-default > org.codehaus.plexus:plexus-utils > org.antlr:antlr > org.antlr:ST4 > org.antlr:antlr3-maven-plugin > > Guess usually these are dependencies seem to be used by the Maven build > and not the built software. This usually isn't mentioned in LICENSE files. > > - If org.hamcrest:hamcrest-core is mentioned, so should > org.hamcrest:hamcrest-library > > - Then sometimes multiple different versions of one library are used, > which is not desirable. > > - Why are there two versions of NOTICE files (Haven't checked the content > as it was quite excessive) > > - There doesn't seem to be a RELEASE_NOTES file > > - The maven-wrapper should be updated to the latest version as that > version invalidly contained an Apache header which suggests it's an Apache > Software. This has been brought up in the incubator list and will probably > be mentioned in the future. > Please just update the source files with the latest versions of the > maven-wrapper library. > > So ... now I'll got back to my skiing holidays. Just thought I'd report > that ... not sure if these findings are release-breakers, however it might > be a good idea to address and/or discuss them soon. > > Chris > > > Am 10.03.19, 10:42 schrieb "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 entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > From: 吴晟 Sheng Wu > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may > be interesting in the changes of old versions, in order to choose right > version. > And, make sense to create a new branch to do release, and versiob update. > You could make the version to 0.9.0-snapshot, after t
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, The url is https://repo1.maven.org/maven2/org/apache/maven/apache-maven/3.5.0/apache-maven-3.5.0-bin.zip. Should we upgrade to maven 3.5.2 or which version should we upgrade to? Thanks XuYi On 3/12/2019 15:37，Jiaye Wu wrote： Hi Xuyi, Do you refer to the version in https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties ? Thanks, Jiaye On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: Hi, As you mentioned "The maven-wrapper should be updated to the latest version", but I did not find anything related to maven wrapper version? Thanks XuYi On 3/11/2019 02:31，Christofer Dutz wrote： 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 results. I did notice that the pom doesn't have an asc (signature), but the sha512 look ok. - The LICANSE file contains invalid paths ... ql/src/java/org/apache/hadoop/hive/ql/ These don't exist, but seem to have to be changed to: iotdb/src/java/org/apache/hadoop/hive/ql/ However these files don't seem to exist at all: iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java - Why is there two LICENSE files? This is quite unusual. - The binary version references libraries that seem to be referenced by the build: joda-time:joda-time org.apache.maven.wagon:wagon-provider-api org.apache.maven:maven-artifact org.apache.maven:maven-artifact-manager org.apache.maven:maven-model org.apache.maven:maven-plugin-api org.apache.maven:maven-profile org.apache.maven:maven-project org.apache.maven:Maven-repository-metadata org.apache.thrift:Libthrift (should be lower-case libthrift) org.codehaus.plexus:plexus-compiler-api org.codehaus.plexus:plexus-container-default org.codehaus.plexus:plexus-utils org.antlr:antlr org.antlr:ST4 org.antlr:antlr3-maven-plugin Guess usually these are dependencies seem to be used by the Maven build and not the built software. This usually isn't mentioned in LICENSE files. - If org.hamcrest:hamcrest-core is mentioned, so should org.hamcrest:hamcrest-library - Then sometimes multiple different versions of one library are used, which is not desirable. - Why are there two versions of NOTICE files (Haven't checked the content as it was quite excessive) - There doesn't seem to be a RELEASE_NOTES file - The maven-wrapper should be updated to the latest version as that version invalidly contained an Apache header which suggests it's an Apache Software. This has been brought up in the incubator list and will probably be mentioned in the future. Please just update the source files with the latest versions of the maven-wrapper library. So ... now I'll got back to my skiing holidays. Just thought I'd report that ... not sure if these findings are release-breakers, however it might be a good idea to address and/or discuss them soon. Chris Am 10.03.19, 10:42 schrieb "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 entry for the next version is added. Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________ From: 吴晟 Sheng Wu Sent: Sunday, March 10, 2019 4:53:00 AM To: dev; dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You could make the version to 0.9.0-snapshot, after the release branch created. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. ------ Original ---------- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:48 AM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月10日周日 上午4:07写道： Hi all, I just prepared the initial version of the RELEASE_NOTES as PR in [1]. I just integrated all closed Jira issues. Now we shoul
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi Xuyi, Do you refer to the version in https://github.com/apache/incubator-iotdb/blob/master/.mvn/wrapper/maven-wrapper.properties ? Thanks, Jiaye On Tue, Mar 12, 2019 at 3:27 PM 徐毅 wrote: > Hi, > > > As you mentioned "The maven-wrapper should be updated to the latest > version", but I did not find anything related to maven wrapper version? > > > Thanks > XuYi > On 3/11/2019 02:31，Christofer Dutz wrote： > 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 results. I did notice that the pom doesn't > have an asc (signature), but the sha512 look ok. > > - The LICANSE file contains invalid paths ... > ql/src/java/org/apache/hadoop/hive/ql/ > These don't exist, but seem to have to be changed to: > iotdb/src/java/org/apache/hadoop/hive/ql/ > However these files don't seem to exist at all: > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java > iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java > > - Why is there two LICENSE files? This is quite unusual. > > - The binary version references libraries that seem to be referenced by > the build: > joda-time:joda-time > org.apache.maven.wagon:wagon-provider-api > org.apache.maven:maven-artifact > org.apache.maven:maven-artifact-manager > org.apache.maven:maven-model > org.apache.maven:maven-plugin-api > org.apache.maven:maven-profile > org.apache.maven:maven-project > org.apache.maven:Maven-repository-metadata > org.apache.thrift:Libthrift (should be lower-case libthrift) > org.codehaus.plexus:plexus-compiler-api > org.codehaus.plexus:plexus-container-default > org.codehaus.plexus:plexus-utils > org.antlr:antlr > org.antlr:ST4 > org.antlr:antlr3-maven-plugin > > Guess usually these are dependencies seem to be used by the Maven build > and not the built software. This usually isn't mentioned in LICENSE files. > > - If org.hamcrest:hamcrest-core is mentioned, so should > org.hamcrest:hamcrest-library > > - Then sometimes multiple different versions of one library are used, > which is not desirable. > > - Why are there two versions of NOTICE files (Haven't checked the content > as it was quite excessive) > > - There doesn't seem to be a RELEASE_NOTES file > > - The maven-wrapper should be updated to the latest version as that > version invalidly contained an Apache header which suggests it's an Apache > Software. This has been brought up in the incubator list and will probably > be mentioned in the future. > Please just update the source files with the latest versions of the > maven-wrapper library. > > So ... now I'll got back to my skiing holidays. Just thought I'd report > that ... not sure if these findings are release-breakers, however it might > be a good idea to address and/or discuss them soon. > > Chris > > > Am 10.03.19, 10:42 schrieb "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 entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > From: 吴晟 Sheng Wu > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may > be interesting in the changes of old versions, in order to choose right > version. > And, make sense to create a new branch to do release, and versiob update. > You could make the version to 0.9.0-snapshot, after the release branch > created. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: Xiangdong Huang > Date: Sun,Mar 10,2019 11:48 AM > To: dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Do we put this release note into the master branch, or create a new branch > called branch-0.8.0 and put this note i
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, As you mentioned "The maven-wrapper should be updated to the latest version", but I did not find anything related to maven wrapper version? Thanks XuYi On 3/11/2019 02:31，Christofer Dutz wrote： 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 results. I did notice that the pom doesn't have an asc (signature), but the sha512 look ok. - The LICANSE file contains invalid paths ... ql/src/java/org/apache/hadoop/hive/ql/ These don't exist, but seem to have to be changed to: iotdb/src/java/org/apache/hadoop/hive/ql/ However these files don't seem to exist at all: iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java - Why is there two LICENSE files? This is quite unusual. - The binary version references libraries that seem to be referenced by the build: joda-time:joda-time org.apache.maven.wagon:wagon-provider-api org.apache.maven:maven-artifact org.apache.maven:maven-artifact-manager org.apache.maven:maven-model org.apache.maven:maven-plugin-api org.apache.maven:maven-profile org.apache.maven:maven-project org.apache.maven:Maven-repository-metadata org.apache.thrift:Libthrift (should be lower-case libthrift) org.codehaus.plexus:plexus-compiler-api org.codehaus.plexus:plexus-container-default org.codehaus.plexus:plexus-utils org.antlr:antlr org.antlr:ST4 org.antlr:antlr3-maven-plugin Guess usually these are dependencies seem to be used by the Maven build and not the built software. This usually isn't mentioned in LICENSE files. - If org.hamcrest:hamcrest-core is mentioned, so should org.hamcrest:hamcrest-library - Then sometimes multiple different versions of one library are used, which is not desirable. - Why are there two versions of NOTICE files (Haven't checked the content as it was quite excessive) - There doesn't seem to be a RELEASE_NOTES file - The maven-wrapper should be updated to the latest version as that version invalidly contained an Apache header which suggests it's an Apache Software. This has been brought up in the incubator list and will probably be mentioned in the future. Please just update the source files with the latest versions of the maven-wrapper library. So ... now I'll got back to my skiing holidays. Just thought I'd report that ... not sure if these findings are release-breakers, however it might be a good idea to address and/or discuss them soon. Chris Am 10.03.19, 10:42 schrieb "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 entry for the next version is added. Chris Outlook für Android<https://aka.ms/ghei36> herunterladen ________________ From: 吴晟 Sheng Wu Sent: Sunday, March 10, 2019 4:53:00 AM To: dev; dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You could make the version to 0.9.0-snapshot, after the release branch created. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. ------ Original ---------- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:48 AM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月10日周日 上午4:07写道： Hi all, I just prepared the initial version of the RELEASE_NOTES as PR in [1]. I just integrated all closed Jira issues. Now we should try to add all further (mentionable) improvements. Personally, I think this is not to crucial as this is the first apache release, so the question "what changed" or what changed incompatible is not that crucial as for further releases. Best Julian https://github.com/apache/incubator-iotdb/pull/91 Am 09.03.19, 11:48 schrieb "Justin Mclean" : Hi, In brief, there are four steps: (
Re: Do we have a plan to release the first normal version of IoTDB this month?
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 the file there (as done in my PR #91).
Julian
Von meinem Mobiltelefon gesendet
Ursprüngliche Nachricht
Betreff: Re: Do we have a plan to release the first normal version of IoTDB
this month?
Von: Christofer Dutz
An: [email protected]
Cc:
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 entry for
the next version is added.
Chris
Outlook für Android<https://aka.ms/ghei36> herunterladen
From: 吴晟 Sheng Wu
Sent: Sunday, March 10, 2019 4:53:00 AM
To: dev; dev
Subject: Re: Do we have a plan to release the first normal version of IoTDB
this month?
Hi.
Release note should be kept in master or further codes, I think. Users may
be interesting in the changes of old versions, in order to choose right version.
And, make sense to create a new branch to do release, and versiob update.
You could make the version to 0.9.0-snapshot, after the release branch created.
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
From Wu Sheng 's phone.
-- Original --
From: Xiangdong Huang
Date: Sun,Mar 10,2019 11:48 AM
To: dev
Subject: Re: Do we have a plan to release the first normal version of IoTDB
this month?
Hi,
Do we put this release note into the master branch, or create a new branch
called branch-0.8.0 and put this note into that branch?
(In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT)
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Julian Feinauer 于2019年3月10日周日 上午4:07写道：
> Hi all,
>
> I just prepared the initial version of the RELEASE_NOTES as PR in [1].
> I just integrated all closed Jira issues.
> Now we should try to add all further (mentionable) improvements.
> Personally, I think this is not to crucial as this is the first apache
> release, so the question "what changed" or what changed incompatible is
not
> that crucial as for further releases.
>
> Best
> Julian
>
> https://github.com/apache/incubator-iotdb/pull/91
>
> Am 09.03.19, 11:48 schrieb "Justin Mclean" :
>
> Hi,
>
> > In brief, there are four steps: (1) setting Maven configuration; (2)
> > creating the release branch and prepare the codebase; (3) mvn
> release and
> > deploy and so on; (4) vote.
>
> You also need to check the LICENSE, NOTICE and DISCLAIMER files in the
> release and we can help you with that.
>
> Thanks,
> Justin
>
>
Re: Do we have a plan to release the first normal version of IoTDB this month?
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 results. I did notice that the pom doesn't have
an asc (signature), but the sha512 look ok.
- The LICANSE file contains invalid paths ...
ql/src/java/org/apache/hadoop/hive/ql/
These don't exist, but seem to have to be changed to:
iotdb/src/java/org/apache/hadoop/hive/ql/
However these files don't seem to exist at all:
iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTErrorNode.java
iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNodeOrigin.java
iotdb /src/java/org/apache/hadoop/hive/ql/parse/ASTNode.java
- Why is there two LICENSE files? This is quite unusual.
- The binary version references libraries that seem to be referenced by the
build:
joda-time:joda-time
org.apache.maven.wagon:wagon-provider-api
org.apache.maven:maven-artifact
org.apache.maven:maven-artifact-manager
org.apache.maven:maven-model
org.apache.maven:maven-plugin-api
org.apache.maven:maven-profile
org.apache.maven:maven-project
org.apache.maven:Maven-repository-metadata
org.apache.thrift:Libthrift (should be lower-case libthrift)
org.codehaus.plexus:plexus-compiler-api
org.codehaus.plexus:plexus-container-default
org.codehaus.plexus:plexus-utils
org.antlr:antlr
org.antlr:ST4
org.antlr:antlr3-maven-plugin
Guess usually these are dependencies seem to be used by the Maven build and not
the built software. This usually isn't mentioned in LICENSE files.
- If org.hamcrest:hamcrest-core is mentioned, so should
org.hamcrest:hamcrest-library
- Then sometimes multiple different versions of one library are used, which is
not desirable.
- Why are there two versions of NOTICE files (Haven't checked the content as it
was quite excessive)
- There doesn't seem to be a RELEASE_NOTES file
- The maven-wrapper should be updated to the latest version as that version
invalidly contained an Apache header which suggests it's an Apache Software.
This has been brought up in the incubator list and will probably be mentioned
in the future.
Please just update the source files with the latest versions of the
maven-wrapper library.
So ... now I'll got back to my skiing holidays. Just thought I'd report that
... not sure if these findings are release-breakers, however it might be a good
idea to address and/or discuss them soon.
Chris
Am 10.03.19, 10:42 schrieb "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 entry for
the next version is added.
Chris
Outlook für Android<https://aka.ms/ghei36> herunterladen
From: 吴晟 Sheng Wu
Sent: Sunday, March 10, 2019 4:53:00 AM
To: dev; dev
Subject: Re: Do we have a plan to release the first normal version of IoTDB
this month?
Hi.
Release note should be kept in master or further codes, I think. Users may
be interesting in the changes of old versions, in order to choose right version.
And, make sense to create a new branch to do release, and versiob update.
You could make the version to 0.9.0-snapshot, after the release branch created.
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
From Wu Sheng 's phone.
-- Original ----------
From: Xiangdong Huang
Date: Sun,Mar 10,2019 11:48 AM
To: dev
Subject: Re: Do we have a plan to release the first normal version of IoTDB
this month?
Hi,
Do we put this release note into the master branch, or create a new branch
called branch-0.8.0 and put this note into that branch?
(In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT)
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Julian Feinauer 于2019年3月10日周日 上午4:07写道：
> Hi all,
>
> I just prepared the initial version of the RELEASE_NOTES as PR in [1].
> I just integrated all closed Jira issues.
> Now we should try to add all further (mentionable) improvements.
> Personally, I think this is not to crucial as this is the first apache
> release, so the question "what changed" or what changed incompatible is
not
> that crucial as for further releases.
>
> Best
> Julian
>
> https://github.com/apache/incubato
Re: Do we have a plan to release the first normal version of IoTDB this month?
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 "master" and "dev" is clear. If so, I agree to use this model. By the way, if so, I think the "master" branch just is used to tell us what the codes are in the latest tag. E.g., there is no difference between the master branch and tag v1.1.0 in the last example of the document. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月11日周一 上午12:07写道： > Full ack... See the explanation in > https://datasift.github.io/gitflow/IntroducingGitFlow.html > > I suggest that we start a vote to move over to such a branching / > development model. > > Julian > > Von meinem Mobiltelefon gesendet > > > ---- Ursprüngliche Nachricht ---- > Betreff: Re: Do we have a plan to release the first normal version of > IoTDB this month? > Von: 吴晟 Sheng Wu > An: dev ,dev > Cc: > > > 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. Unless you have very complex e2e tests in many many scenarios. > > > The release branch is more about do release testing and bug fixed there > before release. After release done, merge to master and release branch > become inactive, unless hotfix release is required. > > > This is my suggestion and my prefer way to run project. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ------ Original -- > From: Xiangdong Huang > Date: Sun,Mar 10,2019 11:44 PM > To: dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > 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 CI test is enough complete), then if we merge > it into the master, we can guarantee the master is also stable.. So I do > not maintain the dev branch anymore.. > > Best, > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer 于2019年3月10日周日 下午5:57写道： > > > 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 have a plan to release the first normal version of > > IoTDB this month? > > Von: Christofer Dutz > > An: [email protected] > > Cc: > > > > 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 > entry > > for the next version is added. > > > > Chris > > > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > > > > From: 吴晟 Sheng Wu > > Sent: Sunday, March 10, 2019 4:53:00 AM > > To: dev; dev > > Subject: Re: Do we have a plan to release the first normal version of > > IoTDB this month? > > > > Hi. > > > > > > Release note should be kept in master or further codes, I think. Users > may > > be interesting in the changes of old versions, in order to choose right > > version. > > And, make sense to create a new branch to do release, and versiob update. > > You could make the version to 0.9.0-snapshot, after the release branch > > created. > > > > > > > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > > > From Wu Sheng 's phone. > > > > &
Re: Do we have a plan to release the first normal version of IoTDB this month?
> 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. Unless you have very complex e2e tests in many many scenarios. The release branch is more about do release testing and bug fixed there before release. After release done, merge to master and release branch become inactive, unless hotfix release is required. This is my suggestion and my prefer way to run project. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:44 PM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? 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 CI test is enough complete), then if we merge it into the master, we can guarantee the master is also stable.. So I do not maintain the dev branch anymore.. Best, --- Xiangdong Huang School of Software, Tsinghua University ?? Julian Feinauer ??2019??3??10?? 5:57?? > 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 have a plan to release the first normal version of > IoTDB this month? > Von: Christofer Dutz > An: [email protected] > Cc: > > 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 entry > for the next version is added. > > Chris > > Outlook f??r Android<https://aka.ms/ghei36> herunterladen > > ____________________ > From: ???? Sheng Wu > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may > be interesting in the changes of old versions, in order to choose right > version. > And, make sense to create a new branch to do release, and versiob update. > You could make the version to 0.9.0-snapshot, after the release branch > created. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: Xiangdong Huang > Date: Sun,Mar 10,2019 11:48 AM > To: dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Do we put this release note into the master branch, or create a new branch > called branch-0.8.0 and put this note into that branch? > (In the pom file of the master branch, the version is still > 0.8.0-SNAPSHOT) > > Best, > > --- > Xiangdong Huang > School of Software, Tsinghua University > > ?? > > > > Julian Feinauer ??2019??3??10?? > 4:07?? > > > Hi all, > > > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > > I just integrated all closed Jira issues. > > Now we should try to add all further (mentionable) improvements. > > Personally, I think this is not to crucial as this is the first apache > > release, so the question "what changed" or what changed incompatible is > not > > that crucial as for further releases. > > > > Best > > Julian > > > > https://github.com/apache/incubator-iotdb/pull/91 > > > > ?1?3Am 09.03.19, 11:48 schrieb "Justin Mclean" : > > > > Hi, > > > > > In brief, there are four steps: (1) setting Maven configuration; > (2) > > > creating the release branch and prepare the codebase; (3) mvn > > release and > > > deploy and so on; (4) vote. > > > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in > the > > release and we can help you with that. > > > > Thanks, > > Justin > > > > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
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 CI test is enough complete), then if we merge it into the master, we can guarantee the master is also stable.. So I do not maintain the dev branch anymore.. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月10日周日 下午5:57写道： > 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 have a plan to release the first normal version of > IoTDB this month? > Von: Christofer Dutz > An: [email protected] > Cc: > > 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 entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > ________________ > From: 吴晟 Sheng Wu > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may > be interesting in the changes of old versions, in order to choose right > version. > And, make sense to create a new branch to do release, and versiob update. > You could make the version to 0.9.0-snapshot, after the release branch > created. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ------ Original -- > From: Xiangdong Huang > Date: Sun,Mar 10,2019 11:48 AM > To: dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Do we put this release note into the master branch, or create a new branch > called branch-0.8.0 and put this note into that branch? > (In the pom file of the master branch, the version is still > 0.8.0-SNAPSHOT) > > Best, > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer 于2019年3月10日周日 上午4:07写道： > > > Hi all, > > > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > > I just integrated all closed Jira issues. > > Now we should try to add all further (mentionable) improvements. > > Personally, I think this is not to crucial as this is the first apache > > release, so the question "what changed" or what changed incompatible is > not > > that crucial as for further releases. > > > > Best > > Julian > > > > https://github.com/apache/incubator-iotdb/pull/91 > > > > Am 09.03.19, 11:48 schrieb "Justin Mclean" : > > > > Hi, > > > > > In brief, there are four steps: (1) setting Maven configuration; > (2) > > > creating the release branch and prepare the codebase; (3) mvn > > release and > > > deploy and so on; (4) vote. > > > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in > the > > release and we can help you with that. > > > > Thanks, > > Justin > > > > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
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 entry for the next version is added. Chris Outlook f??r Android<https://aka.ms/ghei36> herunterladen From: Sheng Wu Sent: Sunday, March 10, 2019 4:53:00 AM To: dev; dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You could make the version to 0.9.0-snapshot, after the release branch created. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin >From Wu Sheng 's phone. -- Original -- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:48 AM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT) Best, --- Xiangdong Huang School of Software, Tsinghua University ?? Julian Feinauer ??2019??3??10?? 4:07?? > Hi all, > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > I just integrated all closed Jira issues. > Now we should try to add all further (mentionable) improvements. > Personally, I think this is not to crucial as this is the first apache > release, so the question "what changed" or what changed incompatible is not > that crucial as for further releases. > > Best > Julian > > https://github.com/apache/incubator-iotdb/pull/91 > > ?1?3Am 09.03.19, 11:48 schrieb "Justin Mclean" : > > Hi, > > > In brief, there are four steps: (1) setting Maven configuration; (2) > > creating the release branch and prepare the codebase; (3) mvn > release and > > deploy and so on; (4) vote. > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in the > release and we can help you with that. > > Thanks, > Justin > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi. Release note should be kept in master or further codes, I think. Users may be interesting in the changes of old versions, in order to choose right version. And, make sense to create a new branch to do release, and versiob update. You could make the version to 0.9.0-snapshot, after the release branch created. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Xiangdong Huang Date: Sun,Mar 10,2019 11:48 AM To: dev Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT) Best, --- Xiangdong Huang School of Software, Tsinghua University ?? Julian Feinauer ??2019??3??10?? 4:07?? > Hi all, > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > I just integrated all closed Jira issues. > Now we should try to add all further (mentionable) improvements. > Personally, I think this is not to crucial as this is the first apache > release, so the question "what changed" or what changed incompatible is not > that crucial as for further releases. > > Best > Julian > > https://github.com/apache/incubator-iotdb/pull/91 > > ?1?3Am 09.03.19, 11:48 schrieb "Justin Mclean" : > > Hi, > > > In brief, there are four steps: (1) setting Maven configuration; (2) > > creating the release branch and prepare the codebase; (3) mvn > release and > > deploy and so on; (4) vote. > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in the > release and we can help you with that. > > Thanks, > Justin > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, Do we put this release note into the master branch, or create a new branch called branch-0.8.0 and put this note into that branch? (In the pom file of the master branch, the version is still 0.8.0-SNAPSHOT) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月10日周日 上午4:07写道： > Hi all, > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > I just integrated all closed Jira issues. > Now we should try to add all further (mentionable) improvements. > Personally, I think this is not to crucial as this is the first apache > release, so the question "what changed" or what changed incompatible is not > that crucial as for further releases. > > Best > Julian > > https://github.com/apache/incubator-iotdb/pull/91 > > Am 09.03.19, 11:48 schrieb "Justin Mclean" : > > Hi, > > > In brief, there are four steps: (1) setting Maven configuration; (2) > > creating the release branch and prepare the codebase; (3) mvn > release and > > deploy and so on; (4) vote. > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in the > release and we can help you with that. > > Thanks, > Justin > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi all, I just prepared the initial version of the RELEASE_NOTES as PR in [1]. I just integrated all closed Jira issues. Now we should try to add all further (mentionable) improvements. Personally, I think this is not to crucial as this is the first apache release, so the question "what changed" or what changed incompatible is not that crucial as for further releases. Best Julian https://github.com/apache/incubator-iotdb/pull/91 Am 09.03.19, 11:48 schrieb "Justin Mclean" : Hi, > In brief, there are four steps: (1) setting Maven configuration; (2) > creating the release branch and prepare the codebase; (3) mvn release and > deploy and so on; (4) vote. You also need to check the LICENSE, NOTICE and DISCLAIMER files in the release and we can help you with that. Thanks, Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > In brief, there are four steps: (1) setting Maven configuration; (2) > creating the release branch and prepare the codebase; (3) mvn release and > deploy and so on; (4) vote. You also need to check the LICENSE, NOTICE and DISCLAIMER files in the release and we can help you with that. Thanks, Justin
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, I find an interesting tool: https://github.com/github-tools/github-release-notes By running `gren changelog --generate`, it can detect what tags the repo has, and then generate a CHANGES.md file. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年3月9日周六 下午3:25写道： > Hi, > > many projects use the Jira release feature for managing the tickets > /features that should go into a release. > So I think it could help to ensure that all activity is mirrored in Jira > issues where we can decide which one to include for the release and what > not. > > Regarding release notes I think we can start simple with the project > description and a general project overview and perhaps a list of recently > added features. > A good start could be to borrow a release notes file from some other > project as basis. > > @chris: are all the maven profiles similar to plc4x or are changes > necessary? > > Julian > > Von meinem Mobiltelefon gesendet > > > ---- Ursprüngliche Nachricht ---- > Betreff: Re: Do we have a plan to release the first normal version of > IoTDB this month? > Von: Xiangdong Huang > An: [email protected] > Cc: > > Hi, > > > We can make a release plan in the dev list first. > > I read the document that Chris gave last month, > http://plc4x.apache.org/developers/release.html > > In brief, there are four steps: (1) setting Maven configuration; (2) > creating the release branch and prepare the codebase; (3) mvn release and > deploy and so on; (4) vote. > > I think we need to discuss the second step, creating a release branch: > (1) which functions are included in this release (I mean, what functions > are not prepared for release, and is the release version is consistent with > current document)? > (2) prepare the release-note. Can someone share with us the best practice > to generate a release note? (I have no experience about that...) > > Best, > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Willem Jiang 于2019年3月9日周六 上午10:27写道： > > > We can make a release plan in the dev list first. > > From my experience , there are lots of details need to go through in > > the first preview version. > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Fri, Mar 8, 2019 at 4:16 PM Xiangdong Huang > wrote: > > > > > > That's Great! A binary release version is really needed! > > > > > > And, if so, at least users can get iotdb-jdbc jars from Maven central > > > repository... > > > > > > Best, > > > --- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > > > > > > > > Christofer Dutz 于2019年3月8日周五 下午3:29写道： > > > > > > > I think that's a good idea, > > > > > > > > I think I might start pre-reviewing the current state ... No need in > > > > listing findings after a RC. > > > > > > > > Chris > > > > > > > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > > > > > > > > > > From: Julian Feinauer > > > > Sent: Friday, March 8, 2019 8:03:46 AM > > > > To: [email protected] > > > > Subject: AW: Do we have a plan to release the first normal version of > > > > IoTDB this month? > > > > > > > > Hi, > > > > > > > > I think a (first apache) release is a good idea. Especially to allow > > > > people to play around with the artifacts. > > > > > > > > After what I have seen the code quality is good and the main > > functionality > > > > works well. > > > > > > > > Julian > > > > > > > > > > > > ---- Ursprüngliche Nachricht ---- > > > > Betreff: Re: Do we have a plan to release the first normal version of > > > > IoTDB this month? > > > > Von: 吴晟 Sheng Wu > > > > An: dev ,dev > > > > Cc: > > > > > > > > I think we should try to do a release. At least a preview version. 3 > > > > months are not short time for a new project. > > > > Of source, no rush, just when you think it is ready and make sense. > > > > > > > > > > > > > > > > Sheng Wu > > > > Apache SkyWalking, ShardingSphere, Zipkin > > > > > > > > From Wu Sheng 's phone. > > > > > > > > > > > > -- Original -- > > > > From: yi xu > > > > Date: Fri,Mar 8,2019 11:09 AM > > > > To: [email protected] > > > > Subject: Re: Do we have a plan to release the first normal version of > > > > IoTDB this month? > > > > > > > > > > > > > > > > Hi, > > > > > > > > Over the last three months, we have improved IoTDB in several ways, > > such > > > > as code quality, document and read/write performance. So should we > > release > > > > a normal version to our users since we don’t have a normal version > > right > > > > now. > > > > > > > > Thanks > > > > XuYi > > > > > > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
Hi, > We can make a release plan in the dev list first. I read the document that Chris gave last month, http://plc4x.apache.org/developers/release.html In brief, there are four steps: (1) setting Maven configuration; (2) creating the release branch and prepare the codebase; (3) mvn release and deploy and so on; (4) vote. I think we need to discuss the second step, creating a release branch: (1) which functions are included in this release (I mean, what functions are not prepared for release, and is the release version is consistent with current document)? (2) prepare the release-note. Can someone share with us the best practice to generate a release note? (I have no experience about that...) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Willem Jiang 于2019年3月9日周六 上午10:27写道： > We can make a release plan in the dev list first. > From my experience , there are lots of details need to go through in > the first preview version. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Fri, Mar 8, 2019 at 4:16 PM Xiangdong Huang wrote: > > > > That's Great! A binary release version is really needed! > > > > And, if so, at least users can get iotdb-jdbc jars from Maven central > > repository... > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > > Christofer Dutz 于2019年3月8日周五 下午3:29写道： > > > > > I think that's a good idea, > > > > > > I think I might start pre-reviewing the current state ... No need in > > > listing findings after a RC. > > > > > > Chris > > > > > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > > > > > > > From: Julian Feinauer > > > Sent: Friday, March 8, 2019 8:03:46 AM > > > To: [email protected] > > > Subject: AW: Do we have a plan to release the first normal version of > > > IoTDB this month? > > > > > > Hi, > > > > > > I think a (first apache) release is a good idea. Especially to allow > > > people to play around with the artifacts. > > > > > > After what I have seen the code quality is good and the main > functionality > > > works well. > > > > > > Julian > > > > > > > > > Ursprüngliche Nachricht > > > Betreff: Re: Do we have a plan to release the first normal version of > > > IoTDB this month? > > > Von: 吴晟 Sheng Wu > > > An: dev ,dev > > > Cc: > > > > > > I think we should try to do a release. At least a preview version. 3 > > > months are not short time for a new project. > > > Of source, no rush, just when you think it is ready and make sense. > > > > > > > > > > > > Sheng Wu > > > Apache SkyWalking, ShardingSphere, Zipkin > > > > > > From Wu Sheng 's phone. > > > > > > > > > -- Original -- > > > From: yi xu > > > Date: Fri,Mar 8,2019 11:09 AM > > > To: [email protected] > > > Subject: Re: Do we have a plan to release the first normal version of > > > IoTDB this month? > > > > > > > > > > > > Hi, > > > > > > Over the last three months, we have improved IoTDB in several ways, > such > > > as code quality, document and read/write performance. So should we > release > > > a normal version to our users since we don’t have a normal version > right > > > now. > > > > > > Thanks > > > XuYi > > > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
We can make a release plan in the dev list first. >From my experience , there are lots of details need to go through in the first preview version. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Mar 8, 2019 at 4:16 PM Xiangdong Huang wrote: > > That's Great! A binary release version is really needed! > > And, if so, at least users can get iotdb-jdbc jars from Maven central > repository... > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz 于2019年3月8日周五 下午3:29写道： > > > I think that's a good idea, > > > > I think I might start pre-reviewing the current state ... No need in > > listing findings after a RC. > > > > Chris > > > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > > > > From: Julian Feinauer > > Sent: Friday, March 8, 2019 8:03:46 AM > > To: [email protected] > > Subject: AW: Do we have a plan to release the first normal version of > > IoTDB this month? > > > > Hi, > > > > I think a (first apache) release is a good idea. Especially to allow > > people to play around with the artifacts. > > > > After what I have seen the code quality is good and the main functionality > > works well. > > > > Julian > > > > > > Ursprüngliche Nachricht > > Betreff: Re: Do we have a plan to release the first normal version of > > IoTDB this month? > > Von: 吴晟 Sheng Wu > > An: dev ,dev > > Cc: > > > > I think we should try to do a release. At least a preview version. 3 > > months are not short time for a new project. > > Of source, no rush, just when you think it is ready and make sense. > > > > > > > > Sheng Wu > > Apache SkyWalking, ShardingSphere, Zipkin > > > > From Wu Sheng 's phone. > > > > > > -- Original -- > > From: yi xu > > Date: Fri,Mar 8,2019 11:09 AM > > To: [email protected] > > Subject: Re: Do we have a plan to release the first normal version of > > IoTDB this month? > > > > > > > > Hi, > > > > Over the last three months, we have improved IoTDB in several ways, such > > as code quality, document and read/write performance. So should we release > > a normal version to our users since we don’t have a normal version right > > now. > > > > Thanks > > XuYi > >
Re: Do we have a plan to release the first normal version of IoTDB this month?
Sounds great! From: Xiangdong Huang Sent: Friday, March 8, 2019 12:16:18 AM To: [email protected] Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? That's Great! A binary release version is really needed! And, if so, at least users can get iotdb-jdbc jars from Maven central repository... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年3月8日周五 下午3:29写道： > I think that's a good idea, > > I think I might start pre-reviewing the current state ... No need in > listing findings after a RC. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > From: Julian Feinauer > Sent: Friday, March 8, 2019 8:03:46 AM > To: [email protected] > Subject: AW: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi, > > I think a (first apache) release is a good idea. Especially to allow > people to play around with the artifacts. > > After what I have seen the code quality is good and the main functionality > works well. > > Julian > > > ---- Ursprüngliche Nachricht > Betreff: Re: Do we have a plan to release the first normal version of > IoTDB this month? > Von: 吴晟 Sheng Wu > An: dev ,dev > Cc: > > I think we should try to do a release. At least a preview version. 3 > months are not short time for a new project. > Of source, no rush, just when you think it is ready and make sense. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ---------- Original ---------- > From: yi xu > Date: Fri,Mar 8,2019 11:09 AM > To: [email protected] > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Over the last three months, we have improved IoTDB in several ways, such > as code quality, document and read/write performance. So should we release > a normal version to our users since we don’t have a normal version right > now. > > Thanks > XuYi >
Re: Do we have a plan to release the first normal version of IoTDB this month?
That's Great! A binary release version is really needed! And, if so, at least users can get iotdb-jdbc jars from Maven central repository... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年3月8日周五 下午3:29写道： > I think that's a good idea, > > I think I might start pre-reviewing the current state ... No need in > listing findings after a RC. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > > From: Julian Feinauer > Sent: Friday, March 8, 2019 8:03:46 AM > To: [email protected] > Subject: AW: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi, > > I think a (first apache) release is a good idea. Especially to allow > people to play around with the artifacts. > > After what I have seen the code quality is good and the main functionality > works well. > > Julian > > > ---- Ursprüngliche Nachricht > Betreff: Re: Do we have a plan to release the first normal version of > IoTDB this month? > Von: 吴晟 Sheng Wu > An: dev ,dev > Cc: > > I think we should try to do a release. At least a preview version. 3 > months are not short time for a new project. > Of source, no rush, just when you think it is ready and make sense. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ---------- Original ---------- > From: yi xu > Date: Fri,Mar 8,2019 11:09 AM > To: [email protected] > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Over the last three months, we have improved IoTDB in several ways, such > as code quality, document and read/write performance. So should we release > a normal version to our users since we don’t have a normal version right > now. > > Thanks > XuYi >
Re: Do we have a plan to release the first normal version of IoTDB this month?
I think that's a good idea, I think I might start pre-reviewing the current state ... No need in listing findings after a RC. Chris Outlook f??r Android<https://aka.ms/ghei36> herunterladen From: Julian Feinauer Sent: Friday, March 8, 2019 8:03:46 AM To: [email protected] Subject: AW: Do we have a plan to release the first normal version of IoTDB this month? Hi, I think a (first apache) release is a good idea. Especially to allow people to play around with the artifacts. After what I have seen the code quality is good and the main functionality works well. Julian Urspr??ngliche Nachricht ---- Betreff: Re: Do we have a plan to release the first normal version of IoTDB this month? Von: Sheng Wu An: dev ,dev Cc: I think we should try to do a release. At least a preview version. 3 months are not short time for a new project. Of source, no rush, just when you think it is ready and make sense. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin >From Wu Sheng 's phone. -- Original -- From: yi xu Date: Fri,Mar 8,2019 11:09 AM To: [email protected] Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Over the last three months, we have improved IoTDB in several ways, such as code quality, document and read/write performance. So should we release a normal version to our users since we don??t have a normal version right now. Thanks XuYi
Re: Do we have a plan to release the first normal version of IoTDB this month?
I think we should try to do a release. At least a preview version. 3 months are not short time for a new project. Of source, no rush, just when you think it is ready and make sense. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: yi xu Date: Fri,Mar 8,2019 11:09 AM To: [email protected] Subject: Re: Do we have a plan to release the first normal version of IoTDB this month? Hi, Over the last three months, we have improved IoTDB in several ways, such as code quality, document and read/write performance. So should we release a normal version to our users since we don??t have a normal version right now. Thanks XuYi
