[
https://issues.apache.org/jira/browse/IOTDB-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiangdong Huang closed IOTDB-216.
-
Resolution: Fixed
> Release of 0.8.1
>
>
> Ke
> Chris
>>
>> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>>
>>
>> From: Xiangdong Huang
>> Sent: Sunday, September 29, 2019 1:10:11 PM
>> To: dev@iotdb.apache.org
>> Subject: Re: Release of 0
> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>
>
> From: Xiangdong Huang
> Sent: Sunday, September 29, 2019 1:10:11 PM
> To: dev@iotdb.apache.org
> Subject: Re: Release of 0.8.1
>
> Hi,
podlings are supposed to learn before
graduation.
Chris
Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
From: Justin Mclean
Sent: Sunday, September 29, 2019 2:59:10 PM
To: dev@iotdb.apache.org
Subject: Re: Release of 0.8.1
Hi,
> Now as Chris a
Hi,
Thanks Justin.
I will wait until 72hrs passed for next RC2.
> While I’ve not looked in detail at the issues, they seem relatively minor
to me. You’re not a top level project so it’s expected there may be a few
issues, and if they are minor they can be fixed in the next release.
I checked
Hi,
> Now as Chris and Jialin pointed out some issues, I need to release RC2.
I’ve not voted on the release yet and was waiting on other PPMC members to do
so. The PPMC need to be involved here not just the mentors, why haven’t any
other PPMC members voted? A reminder that a -1 vote is not a
t rely on manual editing. In plc4x in the
> Kafka integration module we have an example.
>
> Chris
>
> Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
>
>
> From: Xiangdong Huang
> Sent: Sunday, September 29, 2019 1:10:11 PM
&g
integration module we have an example.
Chris
Holen Sie sich Outlook für Android<https://aka.ms/ghei36>
From: Xiangdong Huang
Sent: Sunday, September 29, 2019 1:10:11 PM
To: dev@iotdb.apache.org
Subject: Re: Release of 0.8.1
Hi,
> then I guess we should s
Hi,
> then I guess we should simply add this to the release documentation
I am writing a "how to release" in Chinese... which will mention this
problem.
Now as Chris and Jialin pointed out some issues, I need to release RC2.
My new question is, what should I do on repository.apache.org? Click
Ah ok ... then I guess we should simply add this to the release documentation
;-)
Chris
Am 28.09.19, 00:32 schrieb "Justin Mclean" :
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 :-)
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
@iotdb.apache.org
Subject: Re: Release of 0.8.1
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
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,
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;>
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
...@github.com/apache/incubator-iotdb.git
>> scm:git:ssh://
>> g...@github.com/apache/incubator-iotdb.git
>> ssh://g...@github.com:apache/incubator-iotdb.git
>> rel/0.8
>>
>>
>> It works for pushing commits (two commitlogs: [
ssh://g...@github.com:apache/incubator-iotdb.git
> rel/0.8
>
>
> It works for pushing commits (two commitlogs: [maven-release-plugin]
> prepare release release/0.8.1 and [maven-release-plugin] prepare for next
> development iteration)
> and create a tag (re
m:apache/incubator-iotdb.git
rel/0.8
It works for pushing commits (two commitlogs: [maven-release-plugin]
prepare release release/0.8.1 and [maven-release-plugin] prepare for next
development iteration)
and create a tag (release-0.8.1) on the remote successfully.
However, when I chec
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
gt;>
>> * Bug about 'serializedSize' in ChunkGroupMetaData.java
>> * https://github.com/apache/incubator-iotdb/pull/396/files
>>
>> --
>> Jialin Qiao
>> School of Software, Tsinghua University
>>
>> 乔嘉林
&
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
;
> 黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao 于2019年9月26日周四 下午1:03写道:
>
>> Hi,
>>
>> may be this PR:
>>
>> * Bug about 'serializedSize' in ChunkGroupMetaData.java
>> * https://github.com/apache/incubator-iotdb/pull/396/files
>>
>> --
&g
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Xiangdong Huang"
> > 发送时间: 2019-09-26 12:37:31 (星期四)
> > 收件人: dev@iotdb.apache.org
> > 抄送:
> > 主题: Re: Release of 0.8.1
> >
> > Hi,
> >
> > I am working on it. Any else
嘉林
清华大学 软件学院
> -原始邮件-
> 发件人: "Xiangdong Huang"
> 发送时间: 2019-09-26 12:37:31 (星期四)
> 收件人: dev@iotdb.apache.org
> 抄送:
> 主题: Re: Release of 0.8.1
>
> Hi,
>
> I am working on it. Any else PRs t
2:37:31 (星期四)
> 收件人: dev@iotdb.apache.org
> 抄送:
> 主题: Re: Release of 0.8.1
>
> Hi,
>
> I am working on it. Any else PRs that should be involved in 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
&
0.8.1 could contain these commits.
>
> Best,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Jialin Qiao (Jira)"
> > 发送时间: 2019-09-17 11:53:00 (星期二)
> > 收
how about starting to release
0.8.1?
I think we can make the release more frequent to let more PPMCs know how to
release.
By the way, as the new API is introduced (session API), I think we can
release a new version 0.9 at the same time.
Hi,
Thanks Jialin.
As there is so many bugs that be solved, how about starting to release
0.8.1?
I think we can make the release more frequent to let more PPMCs know how to
release.
By the way, as the new API is introduced (session API), I think we can
release a new version 0.9 at the same
.
Best,
--
Jialin Qiao
School of Software, Tsinghua University
乔嘉林
清华大学 软件学院
> -原始邮件-
> 发件人: "Jialin Qiao (Jira)"
> 发送时间: 2019-09-17 11:53:00 (星期二)
> 收件人: dev@iotdb.apache.org
> 抄送:
> 主题: [jira] [Created] (IOTDB-216) Release of 0.8.1
>
Jialin Qiao created IOTDB-216:
-
Summary: Release of 0.8.1
Key: IOTDB-216
URL: https://issues.apache.org/jira/browse/IOTDB-216
Project: Apache IoTDB
Issue Type: Task
Reporter: Jialin
40 matches
Mail list logo