Hi all,
First, thanks to all of you for the support. This is my first time to be as
a RM of Apache project and I want to thank all guys. It's because all of
you are so patient to answer my question that I can do this release.
Special thanks go to our Mentors, our committers, and a lot of
Hi,
1 for this. Each time series should be independent because we create them
separately in IoTDB.
This is due to the design of TsFile, maybe we should redesign the TsFile
structure.
Best,
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人:
Hi,
> gpg: data source: http://pgp.mit.edu:11371
Did you try hkps://keys.openpgp.org that seems to be the preferred key server
these days.
Thanks,.
Justin
Hi,
> And looking at the page, it says "Pre-release" on that page for the given RC …
Yep because I changed it to say that :-)
Thanks,
Justin
Wow, that is unexpected and probably something you should also share with infra
if they do not know already...
Thank you very much for bringing it up and spotting it!
Julian
From: Xiangdong Huang
Sent: Friday, September 27, 2019 6:18:09 PM
To:
Hi,
Hm... I finally solve the problem and for *ALL* committers *in China*
please pay attention:
If you do not have a VPN (a regular VPN like L2TP), and you never uploaded
your GPG KEY to a key server,
then you can not use pgp.mit.edu as the destination of the key server...
I think all of you
Hi Julian,
Thanks for your reply. I think I uploaded the key about 20 hours ago, so
does it really need so long time to sync...?
Then I tried to search your key id and Chris's key id on the website (
http://pool.sks-keyservers.net:11371/), the website also says not found...
Best,
Hi,
Hm.. I quickly search some sentences using Google. Indeed, if the contents
are loaded by JS (actually the contents are at the github repo/docs/*.md),
then they will not be indexed.
Any Suggestions? @Zesong @Yi Xu?
By the way, I think the website of PLC4x is good, except a minor issue: on
Hi,
it can take some time fort he keyservers to sync, so this could be one issue.
Just try it again later.
Julian
Am 27.09.19, 16:00 schrieb "Xiangdong Huang" :
Hi all,
Thanks for taking care of this release...
One more question that I am facing...
Now I am
Hi all,
Thanks for taking care of this release...
One more question that I am facing...
Now I am trying to closing the staging repository from the Nexus [1],
but fails because "No public key: Key with id: (2206ef8f64c35889) was not
able to be located on http://pool.sks-keyservers.net:11371;>
Hi all,
today we were discussing things in the PLC4X project especially because our
website looks so crappy.
Julian mentioned the IoTDB website being nice and built with Vue … so I
thought: Isn’t Vue one of these “compile to JS” technologies?
So I checked and indeed it is.
So the next thing I
Yuan Tian created IOTDB-245:
---
Summary: Different types of measurements that have same name in
one storage group should be supported.
Key: IOTDB-245
URL: https://issues.apache.org/jira/browse/IOTDB-245
Hey,
but I think we are totally covered here by Apache Policy as a Release is only a
release (and released) if its source in the svn.
So although this thing has the "name" release in the tag it has strictly
speaking nothing to do with an APACHE release at all.
In fact, this is the practice we
And looking at the page, it says "Pre-release" on that page for the given RC ...
Chris
Am 27.09.19, 11:13 schrieb "Justin Mclean" :
Hi,
OK this is not ideal:
https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1
Because we haven't voted on the release
Definitely not.
This is a problem with Github ... manually doing everything the release plugin
does, just to avoid a problem with an external Non ASF mirror is definitely not
anything I would be willing to do.
The release plugin is built to make correct releases (That’s what it was
created
Hi,
> That's what maven automatically does ... it tags the potential release in the
> repo.
> That Github shows these release tags as "released" versions is a issue that
> has been discussed in the past.
Which I believe why you should do do maven release after you have voted on the
release.
That's what maven automatically does ... it tags the potential release in the
repo.
That Github shows these release tags as "released" versions is a issue that has
been discussed in the past.
Chris
Am 27.09.19, 11:13 schrieb "Justin Mclean" :
Hi,
OK this is not ideal:
Hi,
OK this is not ideal:
https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1
Because we haven't voted on the release yet, you can only release artefacts
once you have voted on them.
I’ve marked it as “pre-release” to hopefully stop any confusion that it has
actually been
Hi,
Well well, I know why I can not find the files from repository.apache.org,
because I did not login on the website..
The document of PLC4x has pointed out that:
> After the build it is important to log in to Nexus at
https://repository.apache.org/, select Staging Repositories and find the
Hi,
I would choose the latter. Reducing unnecessary network traffic sounds more
attractive to me, besides, this may save a lot memory when the fetch size is
quite large.
| |
Tian Jiang
|
|
jt2594...@163.com
|
签名由网易邮箱大师定制
On 9/27/2019 16:22，Lei Rui wrote：
Hi，
I find the bug and the cause is
Hi,
Something to correct:
If I check the rel/0.8 branch in gitbox repo [1], I can find the commitlogs
that maven release plugin generated.
[1]
https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog;h=refs/heads/rel/0.8
But still do not know why repository.apache.org and
Hi，
I find the bug and the cause is that there is divergence between the server and
the client in treating queries with duplicated columns.
For example, I query "select s0,s0,s0,s1 from root.vehicle.d0",
The server returns the result with duplicated fields as queried.
[root.vehicle.d0.s0,
Hi Chris,
Actually now I still meet some issues..
> "git remote set-url
https://gitbox.apache.org/repos/asf/incubator-iotdb.git;
do you mean: git remote set-url --push origin
https://gitbox.apache.org/repos/asf/incubator-iotdb.git ?
(But I think `mvn release:prepare` command choose the git url
Lei Rui created IOTDB-244:
-
Summary: wrong duplicated columns query result
Key: IOTDB-244
URL: https://issues.apache.org/jira/browse/IOTDB-244
Project: Apache IoTDB
Issue Type: Bug
Hi Xiangdong,
this happens when the release plugin tries to commit and push the changes it
does during the release.
It changes the versions to the release versions and commits that and then
changes them to the next development version and then commits a second time.
There seem to be issues with
Hi all,
But the maven release tools are what actually produce the artifacts that we are
going to vote on.
So yes you would do the maven release: This will stage the maven artifacts and
produce a source distribution with pgp signatures and hashes in the root target
folder.
These files you will
The naming is usually handled automatically by the release plugin (Except in
non pom.xml files like documentation and RELEASE_NOTES)
So if you have references to the current SNAPSHOT version in your
RELEASE_NOTES, I would remove the SNAPSHOT manually before running mvn
release:prepare.
(Just
Hi,
I solved it by changing the SCM from https protocol to ssh protocol.
(Howver I feel curious how Julian solved it for the last release..)
I will submit a PR later.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Xiangdong
Hi,
@Justin, many thanks! I have already upload the updated KEYS there.
Now I want to try maven plugin `mvn release:prepare` to automatically
finish some work, like create a tag on github..
However, it fails because:
[ERROR] Failed to execute goal
29 matches
Mail list logo
