Re: Next steps for release 0.8.0-rc1

[Justin Mclean]

Hi,

> Or, we provide a RC1 (which we do not expect to be the final release) but 
> have then the community and the mentors check everything.

I can check it tomorrow (my time). But a quick quick shows a couple of issues:
- Missing incubating in name of artefact
- Jars in the source release
- Name seem wrong "IoTDB Root”?
- Docker file seems to using master?
- Wrong header on this file? /.mvn/wrapper/MavenWrapperDownloader.java
- It not immediately obvious of there is any 3rd party code in the source which 
make license and notice a lot simpler

Also being a first release, as long as there’s not significant issues, i’s 
likely to pass an IPMC vote.

Thanks,
Justin

Re: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hi all,

after everything is setup for the release, EXCEPT for some unclarity with 
regards to LICENSE, NOTICE and binary “supplementary files” I ask myself whats 
the best way to proceed.
Either we check our current material with the help of our mentors (like the PR 
https://github.com/apache/incubator-iotdb/pull/300).

Or, we provide a RC1 (which we do not expect to be the final release) but have 
then the community and the mentors check everything.
Then we can collect all necessary changes and fix them and come back with a RC2 
which will hopefully pass then.

Perhaps the second version is a bit better and clearer and eases things for our 
mentors as its just an RC as they know it and can do their regular checks.

What do others (and also our mentors) think?

Julian

Am 25.07.19, 08:20 schrieb "Julian Feinauer" :

Hi Justin,

from Chris email it should work with:

> You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Julian

Am 25.07.19, 08:18 schrieb "Justin Mclean" :

HI,

> short update on that... INFRA already set up the staging profile on 
nexus and I just did a quick dry-run and everything works.

So how can I locally produce a source release?

Thanks,
Justin

Re: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hi Justin,

from Chris email it should work with:

> You can test what happens during a release by doing a "mvn package -P 
> release,apache-release".

Julian

Am 25.07.19, 08:18 schrieb "Justin Mclean" :

HI,

> short update on that... INFRA already set up the staging profile on nexus 
and I just did a quick dry-run and everything works.

So how can I locally produce a source release?

Thanks,
Justin

Re: Next steps for release 0.8.0-rc1

[Justin Mclean]

HI,

> short update on that... INFRA already set up the staging profile on nexus and 
> I just did a quick dry-run and everything works.

So how can I locally produce a source release?

Thanks,
Justin

Re: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hey all,

short update on that... INFRA already set up the staging profile on nexus and I 
just did a quick dry-run and everything works.
So we are absolutely ready to go for a RC1 as soon as LICENSE and NOTICE 
changes are sorted out (https://github.com/apache/incubator-iotdb/pull/300).

Julian

Am 24.07.19, 13:47 schrieb "Julian Feinauer" :

Hi Chris,

Thanks for the comment.
I already requested a profile at infra 
(https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18788).

But will be good to have your support for the next steps.

Julian

PS: have a nice list day!

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi guys,

I'm actually writing this lying in a sun bed at the beach on creta ;-)

You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Then it should also build the source release artifacts.

The only thing we need to do is that nexus is prepared for the iotdb group 
ID. Without that performing the releases would be a challenge 😉

But feel free to build a test - release with the apache-release profile 
enabled and check the contents of the artifacts. If you already did the release 
prepare, you can even manually build the release.

I'll be traveling home tomorrow so I'll be more accessible to help from 
Friday on.


Chris

Holen Sie sich Outlook für Android


From: Julian Feinauer 
Sent: Wednesday, July 24, 2019 11:21:38 AM
To: dev@iotdb.apache.org 
Subject: AW: Next steps for release 0.8.0-rc1

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x 
which he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think 
the way we used it in plc4x is fine as you only need those artifacts for a 
release and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but 
on most ASF projects you go mvn package and you end up with the source release 
in the target directory.

Anyway Chris is the person to speak to about this, he probably knows what 
needs to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/

Re: IoTDB vs InfluxDB Benchmark Report

[mehedi hasan]

Hi,
I am keen to have a look on the report.
Its interesting to see how good is IoTDB compare to Influx.
Where to check that? Would be nice to have a confluence or sth like that.

best, Mehedi


On Thu, Jul 25, 2019 at 7:49 AM Xiangdong Huang  wrote:

> Hi,
>
> Many thanks for the topic, but mailing list does not support the
> attachment...
>
> How about upload it to IoTDB confluence or just open an JIRA issue to
> discuss about that.
>
> Best,
>
> chengong13...@sangfor.com.cn 于2019年7月25日
> 周四上午11:49写道：
>
> > hello,
> >
> >  Here is the IoTDB vs InfluxDB benchmark test report, which contains
> > the write, read, and compression performance test.
> >  You can check the annex for detail.
> >  Best wishes :-)
> >
> > --
> > chengong13...@sangfor.com.cn
> >
> --
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: IoTDB vs InfluxDB Benchmark Report

[Xiangdong Huang]

Hi,

Many thanks for the topic, but mailing list does not support the
attachment...

How about upload it to IoTDB confluence or just open an JIRA issue to
discuss about that.

Best,

chengong13...@sangfor.com.cn 于2019年7月25日
周四上午11:49写道：

> hello,
>
>  Here is the IoTDB vs InfluxDB benchmark test report, which contains
> the write, read, and compression performance test.
>  You can check the annex for detail.
>  Best wishes :-)
>
> --
> chengong13...@sangfor.com.cn
>
-- 
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

IoTDB vs InfluxDB Benchmark Report

[chengong13...@sangfor.com.cn]

hello,

 Here is the IoTDB vs InfluxDB benchmark test report, which contains the 
write, read, and compression performance test.
 You can check the annex for detail. 
 Best wishes :-)



chengong13...@sangfor.com.cn

[jira] [Created] (IOTDB-153) LIMIT OFFSET clause is unreasonably slow when N and OffsetValue are rather small.

[Lei Rui (JIRA)]

Lei Rui created IOTDB-153:
-

 Summary: LIMIT  OFFSET  clause is unreasonably 
slow when N and OffsetValue are rather small. 
 Key: IOTDB-153
 URL: https://issues.apache.org/jira/browse/IOTDB-153
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Lei Rui






--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Version 0.8.1?

[Julian Feinauer]

Hey,

I found some time and reverted the changes from the first trial in rel/0.8.
So we can simply merge it when the PR is agreed on : )

Julian

Am 24.07.19, 13:42 schrieb "Julian Feinauer" :

Hi xiangdong,

I we should simply revert the rel branch back to before release, this is 
https://github.com/apache/incubator-iotdb/commit/0936b2bd2b9b91bb124affc036fb69505dd4f300

Or you prepare a pr and I'll merge it later.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi Julian,

I see.

I am trying to fix the problem of LICENSE and NOTICE.

So, do I need to submit the PR to release/0.8.0 and cherry-pick them to
rel/0.8 and master branches after the PR is accepted?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月24日周三 下午5:12写道：

> Hi Xiangdong,
>
> There is one tagged commit (tag 'release/0.8.0) in the commit log with
> version 0.8.0. This commit is the code for rc1.
> The rel branch shows 0.8.1 as this would be the next bugfix release for
> 0.8.
>
> Does that clarify your question?
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Version 0.8.1?
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do 
we
> start with 0.8.0 or 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: Licensing / Notice / etc

[Xiangdong Huang]

Hi,

Thanks Justin and Willem.

I have used the maven plugin to check all license once again.

I have finished the above modifications, you can have a check:

[1] License:
https://github.com/apache/incubator-iotdb/blob/2561a3b397fb6fedd99a0afddc4e665f253c5e22/License
[2] License-binary:
https://github.com/apache/incubator-iotdb/blob/2561a3b397fb6fedd99a0afddc4e665f253c5e22/License-binary
[3] Notice:
https://github.com/apache/incubator-iotdb/blob/2561a3b397fb6fedd99a0afddc4e665f253c5e22/NOTICE
[4] Notice-binary:
https://github.com/apache/incubator-iotdb/blob/2561a3b397fb6fedd99a0afddc4e665f253c5e22/NOTICE-binary

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Willem Jiang  于2019年7月24日周三 下午2:16写道：

>  If you have the binary release, you need to list all the third party
> jars in the License file.
> BTW, you can use maven license plugin[1] to list those jars in your
> distribution directory.
> You can find the plugin setting example here[2]. The only missing part
> is you still need to copy the generated file into License file
> yourself.
>
> [1]https://www.mojohaus.org/license-maven-plugin/
> [2]https://github.com/apache/servicecomb-pack/blob/master/pom.xml#L643
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jul 24, 2019 at 10:00 AM Xiangdong Huang 
> wrote:
> >
> > Hi Justin,
> >
> > How about the following modifications:
> >
> > > 1. Why is license information being mentioned in NOTICE? All license
> > information should go in LICENSE.
> >
> > Remove all license information out of NOTICE, and copy all content of
> > NOTICEs from all bundled dependencies to our NOTICE?
> >
> > > 2. Why is the General Public License (GPL) license mentioned? (It’s a
> > Category X license)
> >
> > I check the content and find that we use `javax.annotation`, which uses
> > CDDL and GPL double license.
> > I think it is ok that we use the dependence according to CDDL. So just
> > removing the content about GPL is ok, I think.
> >
> > > 3.  Why are dependancies (JUnit / Hamscrest) which I assume are not
> > bundled mentioned?
> >
> > I think we can remove them out of the NOTICE and LICENSE.
> >
> > > 4. Why are the binaries mentioned in the source release? Please make
> > seperate LICENSE and NOTICE for the source and binary releases.
> >
> > Do we need to maintain 4 files: LICENSE, NOTICE,  LICENSE-binary, and
> > NOTICE-binary?
> >
> > > In LICENSE it also seem you are listing dependancies rather than what
> is
> > bundled in the source release?
> >
> > According to [1] (BUNDLED VS. NON-BUNDLED DEPENDENCIES), only the
> (binary)
> > jars and java (source) files that written by the third part are bundled.
> >
> > The dependencies that claimed in pom.xml  will be downloaded
> automatically
> > from the Maven Repository when the user compile the source code, so they
> > can be considered as non-bundled. Are these dependencies can be removed
> > from the LICENSE?
> >
> > [1] http://www.apache.org/dev/licensing-howto.html#mod-notice
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Justin Mclean  于2019年7月24日周三 上午6:47写道：
> >
> > > HI,
> > >
> > > I took a quick look at NOTICE and something is not right:
> > > 1. Why is license information being mentioned in NOTICE? All license
> > > information should go in LICENSE.
> > > 2. Why is the General Public License (GPL) license mentioned? (It’s a
> > > Category X license)
> > > 3. Why are dependancies (JUnit / Hamscrest) which I assume are not
> bundled
> > > mentioned?
> > > 4. Why are the binaries mentioned in the source release? Please make
> > > seperate LICENSE and NOTICE for the source and binary releases.
> > >
> > > In LICENSE it also seem you are listing dependancies rather than what
> is
> > > bundled in the source release?
> > >
> > > Thanks,
> > > Justin
>

AW: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hi Chris,

Thanks for the comment.
I already requested a profile at infra 
(https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18788).

But will be good to have your support for the next steps.

Julian

PS: have a nice list day!

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi guys,

I'm actually writing this lying in a sun bed at the beach on creta ;-)

You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Then it should also build the source release artifacts.

The only thing we need to do is that nexus is prepared for the iotdb group ID. 
Without that performing the releases would be a challenge 😉

But feel free to build a test - release with the apache-release profile enabled 
and check the contents of the artifacts. If you already did the release 
prepare, you can even manually build the release.

I'll be traveling home tomorrow so I'll be more accessible to help from Friday 
on.


Chris

Holen Sie sich Outlook für Android


From: Julian Feinauer 
Sent: Wednesday, July 24, 2019 11:21:38 AM
To: dev@iotdb.apache.org 
Subject: AW: Next steps for release 0.8.0-rc1

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x which 
he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think the 
way we used it in plc4x is fine as you only need those artifacts for a release 
and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/

AW: Version 0.8.1?

[Julian Feinauer]

Hi xiangdong,

I we should simply revert the rel branch back to before release, this is 
https://github.com/apache/incubator-iotdb/commit/0936b2bd2b9b91bb124affc036fb69505dd4f300

Or you prepare a pr and I'll merge it later.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi Julian,

I see.

I am trying to fix the problem of LICENSE and NOTICE.

So, do I need to submit the PR to release/0.8.0 and cherry-pick them to
rel/0.8 and master branches after the PR is accepted?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月24日周三 下午5:12写道：

> Hi Xiangdong,
>
> There is one tagged commit (tag 'release/0.8.0) in the commit log with
> version 0.8.0. This commit is the code for rc1.
> The rel branch shows 0.8.1 as this would be the next bugfix release for
> 0.8.
>
> Does that clarify your question?
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Version 0.8.1?
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
> start with 0.8.0 or 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: Next steps for release 0.8.0-rc1

[Christofer Dutz]

Hi guys,

I'm actually writing this lying in a sun bed at the beach on creta ;-)

You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Then it should also build the source release artifacts.

The only thing we need to do is that nexus is prepared for the iotdb group ID. 
Without that performing the releases would be a challenge 😉

But feel free to build a test - release with the apache-release profile enabled 
and check the contents of the artifacts. If you already did the release 
prepare, you can even manually build the release.

I'll be traveling home tomorrow so I'll be more accessible to help from Friday 
on.


Chris

Holen Sie sich Outlook für Android


From: Julian Feinauer 
Sent: Wednesday, July 24, 2019 11:21:38 AM
To: dev@iotdb.apache.org 
Subject: AW: Next steps for release 0.8.0-rc1

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x which 
he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think the 
way we used it in plc4x is fine as you only need those artifacts for a release 
and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/

Re: Version 0.8.1?

[Xiangdong Huang]

Hi Julian,

I see.

I am trying to fix the problem of LICENSE and NOTICE.

So, do I need to submit the PR to release/0.8.0 and cherry-pick them to
rel/0.8 and master branches after the PR is accepted?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月24日周三 下午5:12写道：

> Hi Xiangdong,
>
> There is one tagged commit (tag 'release/0.8.0) in the commit log with
> version 0.8.0. This commit is the code for rc1.
> The rel branch shows 0.8.1 as this would be the next bugfix release for
> 0.8.
>
> Does that clarify your question?
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Version 0.8.1?
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
> start with 0.8.0 or 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

AW: Version 0.8.1?

[Julian Feinauer]

Hi Xiangdong,

There is one tagged commit (tag 'release/0.8.0) in the commit log with version 
0.8.0. This commit is the code for rc1.
The rel branch shows 0.8.1 as this would be the next bugfix release for 0.8.

Does that clarify your question?

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
start with 0.8.0 or 0.8.1?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

Version 0.8.1?

[Xiangdong Huang]

Hi,

I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
start with 0.8.0 or 0.8.1?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

AW: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x which 
he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think the 
way we used it in plc4x is fine as you only need those artifacts for a release 
and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/

Re: Next steps for release 0.8.0-rc1

[Justin Mclean]

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/

Re: Next steps for release 0.8.0-rc1

[Justin Mclean]

Hi,

> If I recall correctly it does it only in the release :perform phase which 
> currently fails because we have no profile on nexus :)

That doesn’t seem right to me, you should be able to build the source package 
locally without needing that. Do you know why this is the case? Why not just 
use this? [1]

Thanks,
Justin

1. https://maven.apache.org/plugins/maven-source-plugin/usage.html

AW: Next steps for release 0.8.0-rc1

[Julian Feinauer]

Hey Justin,

If I recall correctly it does it only in the release :perform phase which 
currently fails because we have no profile on nexus :)

So as soon as this is done we should have the correct source package.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> I know and what I meant is that sources will be packaged as tarball by the 
> source release goal from the apache parent maven pom.

Which currently doesn’t seem to create a source package when you do a "mvn 
package”. Hence my confusion of what’s actually in the release or not.

Thanks,
Justin