Re: Rename modules

No objections from my side, at least : ) Am 22.07.19, 15:15 schrieb "Xiangdong Huang" : Hi, If there is no more comments, shall we merge the PR (#289)? Best, --- Xiangdong Huang School of Software, Tsinghua University

Re: Very frequent commits to rel/0.8

Hey, we should extend the package phase to finally combining all of those inside one tar.gz file or something which is then moved to target/ as artefact. Regarding the Voting Process: First, a vote is held on this list. If the RC passes this vote (I will send some details on what one should do

Re: Rename modules

Hi, If there is no more comments, shall we merge the PR (#289)? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年7月22日周一 下午8:58写道： > Hi, > > +1 from me. > Regarding merge-hell...if we use git mv it should

Re: Very frequent commits to rel/0.8

Hi, > PS.: But after that is done I would start the first release candidate and we can move to the next phase which is Checking the RC and Voting : ) Where it occurs, on this mailing list or gene...@incubator.apache.org? Best, --- Xiangdong Huang School of

Re: Very frequent commits to rel/0.8

Hi, I think Jialin has finish some works: Now when we run `mvn package` or `mvn package -DskipTests`, the sbin/, conf/ lib/ will be created in the root folder of the project. I think the rest thing is packing them and other materials (e.g., LICENSE, NOTICE...) as a a tar.gz or zip file. Best,

Re: Very frequent commits to rel/0.8

Hey, before finally preparing the first RC the only thing thats missing from my side is the packaging oft he binaries. As Chris already said, he would offer some help on the maven assembly plugin. Background is that it’s a "delicate" topic in the ASF to provide bundled artefacts alongside

Re: Rename modules

Hi, +1 from me. Regarding merge-hell...if we use git mv it should work out of the box with very few issues I think __ Julian Am 22.07.19, 14:40 schrieb "Xiangdong Huang" : Well, the structure looks fine... I pray for those existing opened PRs because the confliction...

Re: [jira] [Created] (IOTDB-150) Try some other web fonts

+1! Look forward to more artists! --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lei Rui (JIRA) 于2019年7月22日周一 下午8:20写道： > Lei Rui created IOTDB-150: > - > > Summary: Try some other web fonts

Re: Rename modules

Well, the structure looks fine... I pray for those existing opened PRs because the confliction... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年7月22日周一 下午8:22写道： > Hi, > > This idea is excellent! So, the

Re: Rename modules

Hi, This idea is excellent! So, the target folders and artifactIds can be as follows: tsfile : tsfile service-rpc : service-rpc jdbc : iotdb-jdbc client : iotdb-client server: iotdb-server example : iotdb-examples grafana : iotdb-grafana spark-tsfile : spark-tsfile (we may add

[jira] [Created] (IOTDB-150) Try some other web fonts

Lei Rui created IOTDB-150: - Summary: Try some other web fonts Key: IOTDB-150 URL: https://issues.apache.org/jira/browse/IOTDB-150 Project: Apache IoTDB Issue Type: Wish Reporter: Lei Rui

Re: Rename modules

Hey, logically the PR iss mall but many changed files : ) The only thing I would take to consider is whether we really do want those names for folders. In other projects you usually make the short name for the folder and longer for the artifact, this means folders would be like For example

Re: Rename modules

Hi, It is a big change because at least 2/3 files are renamed... Best. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年7月22日周一 下午7:43写道： > Hi all, > > IoTDB project has the following modules: tsfile, service-rpc,

Rename modules

Hi all, IoTDB project has the following modules: tsfile, service-rpc, jdbc, iotdb, grafana, service-rpc, iotdb-cli, example and spark, in which "iotdb" and "spark" look strange. Therefore, I rename iotdb to iotdb-server and spark to spark-tsfile by "git mv" for retaining the commit history

Re: Very frequent commits to rel/0.8

Hi, +1 for DO NOT push more new features into rel/0.8. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年7月22日周一 下午4:24写道： > Hi Xiangdong and Jialin, > > I saw both of your work and agree with both! > So

Re: Very frequent commits to rel/0.8

Hi Xiangdong and Jialin, I saw both of your work and agree with both! So this was no general criticism but rather a sensibilization as I also saw some features that went into. As this release is important for learning I simply took the freedom to put that out explicitly again : ) Julian Am

Re: Very frequent commits to rel/0.8

Hi, I cherry-picked a modification for fixing Travis-CI from the master to rel/0.8 just now, otherwise the branch will fail on Travis... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年7月22日周一 下午3:56写道： > Hi

Re: Very frequent commits to rel/0.8

Hi Julian, Thanks for the introduction. Most of the commits are from PRs that supplement documents of version 0.8.0. However, these PRs went to master. From now on, I will change the target of document-related PRs to rel/0.8.0. Besides, there are two PRs that should be merged to rel/0.8.0.

Very frequent commits to rel/0.8

Hi al, I just checked the git logs and observerd that there are very frequent commits to the branch “rel/0.8”, which should not be the case. So I’ll try to briefly summarize the release process or how the branching model works. The branch rel/0.8 is solely for the preparation for the release.