Hi Chris,
> I inspected the downloaded zip archive and couldn't find the jars.
Did you download the zip file from [1]? The codes come from the
`release/0.8.0` branch, and I tried it can not generated a correct binary
file...
Actually the branch that Jialin tried on is rel/0.8, which can genera
Hi Chris,
I tried once again and find that `release/0.8.0` can generate a 17MB binary
file, too. The previous error is caused by "too many requests" reported by
"org.sonatype.ossindex". However, the tag of release/0.8.0 is out-of-date
because there are many document issues fixed after that.
Now
Hi Xiangdong,
I guess you misunderstand what we're voting on.
We're not voting on the repository, we're voting on the artifacts, that are
staged for release.
In this case:
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc1/apache-iotdb-0.8.0-incubating-source-release.zip
And if y
Short nitpick for you Chris: we do not do binary releases :)
Von meinem Mobiltelefon gesendet
Ursprüngliche Nachricht
Betreff: Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:
Hi Xiangdong,
I guess you misunderstand what we're v
> We're not voting on the repository, we're voting on the artifacts, that
are staged for release.
I see... Actually I did not know about its existence...
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Christofer Dutz 于2019年7月29
Hi Xiangdong,
I am a little puzzled, I have to admit.
Because: [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc1
are actually the artifacts we are voting on. [1] are convenience artifacts
(technically same as the convenience binary distribution under [2])
How can you vote +1
Hi,
We vote what is in the release area not what on GitHub or in the repo,
otherwise we cannot be sure what changes may of been made.
> However, the tag of release/0.8.0 is out-of-date because there are many
> document issues fixed after that.
It needs to be what we voted on. If that tag is ch
HI,
> As Justin voted +1, I think he himself judges those things as minor enough.
Just confirming that this the case, that I think the issues are minor,
especially and this is the first release.
Thanks,
Justin
Hi,
Also when voting on release it's a good idea to list what you checked rather
than saying +1.
There’s a checklist that can be found here [1] that you can use or the project
could come up with it’s own.
Some project try to automate this, but I’d take case in doing so as it sometime
doesn’t
Hi,
thanks Chris and Justin for your comments.
I also want to point to the checklist (which I had in my initial Vote Email)
which I created in our Confluence:
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
Although its important to State that "correct" is only wha
I have mentioned it before but not strongly enough.
Rc1 has issues. The vote on it should be cancelled and an ec2 release
candidate made for a new vote.
It is very common to need a few rc's.
Regards, KAM
On Mon, Jul 29, 2019, 05:21 Justin Mclean wrote:
> Hi,
>
> Also when voting on release i
Hi all,
I'm moving this discussion tot he DISCUSS Thread (answering to Kevins mail).
With Chris vote result I agree with Kevin (and Chris) and also suggest to
Cancel the RC.
I suggest that we make a few necessary fixes to come up with a RC2 soon so that
we get the release out of the door.
Most
Hi,
> I guess it's important for you all to come up with some guidelines (Like
the ones Julian started and which still need a little fine-tuning) which
should be used to verify a release.
> My gut-feeling tells me a lot of +1 votes on this release sort of lack a
little of the thoroughness we would
BUILD-UNSTABLE: Job 'IoTDB-Pipeline/master [master] [145]':
Check console output at "https://builds.apache.org/job/IoTDB-Pipeline/job/master/145/";>IoTDB-Pipeline/master
[master] [145]"
14 matches
Mail list logo
