Re: [DISCUSS] Enable github issue?
Would something like this be an option? https://boardgenius.io/ Seems to be a tool that syncs github issues and jira ... perhaps some tooling down that road would be a good idea? This way the RM doesn't have to maintain the Release Notes with closed issues from multiple systems and people wanting to work on stuff don't have to check two systems. Chris Am 03.01.20, 10:35 schrieb "Xiangdong Huang" : > and it should clearly describe how we work after opening issue absolutely +1 --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 atoiLiu 于2020年1月3日周五 下午4:55写道： > Hi， > I agree with Lei Rui opinion, and it should clearly describe how we work > after opening issue > > Regards， > > > > 在 2020年1月3日，下午4:49，Lei Rui 写道： > > > > I would suggest a formal vote. > > > > > > Regards, > > Lei Rui > > > > > > On 1/3/2020 16:41，Jialin Qiao wrote： > > Hi, > > > > In the discussion about enabling github issues, 5 people support while no > > other voices. > > > > Jialin Qiao > > Minhao Gouwang > > Xiangdong Huang > > Tianci Zhu > > Dawei Liu > > > > I think there is no need to call for a vote. Meanwhile, Jira is also used > > and we could carry the issues to Jira through some tools. > > > > Could someone help enable the github issues? > > > > Thanks, > > > > Jialin Qiao 于2020年1月2日周四 下午4:29写道： > > > > Hi, > > > > Let's continue this discussion or make a decision? > > > > Jialin Qiao 于2019年12月31日周二 下午7:28写道： > > > > Hi, > > > > +1 for managing issues in github. > > +0 for using Jira. > > > > Thanks > > Jialin Qiao > > > > > > > > -- > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > > > > > > > -- > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > >
[jira] [Commented] (IOTDB-400) Support Restful API
[ https://issues.apache.org/jira/browse/IOTDB-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007518#comment-17007518 ] Otto Fowler commented on IOTDB-400: --- or graphql > Support Restful API > --- > > Key: IOTDB-400 > URL: https://issues.apache.org/jira/browse/IOTDB-400 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Jialin Qiao >Priority: Major > > To support different languages, we'd better support a restful api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-400) Support Restful API
Jialin Qiao created IOTDB-400: - Summary: Support Restful API Key: IOTDB-400 URL: https://issues.apache.org/jira/browse/IOTDB-400 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao To support different languages, we'd better support a restful api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[BUILD-FAILURE]: Job 'IoTDB Website [null] [98]'
BUILD-FAILURE: Job 'IoTDB Website [null] [98]': Check console output at "https://builds.apache.org/job/IoTDB%20Website/98/;>IoTDB Website [null] [98]"
Re: [VOTE] Enable github issue
+1 Best, --- Zesong Sun School of Software, Tsinghua University 孙泽嵩 清华大学 软件学院 > 2020年1月3日 20:04，毛东方 写道： > > +1 > > —— > 毛东方 > maod...@mails.tsinghua.edu.cn > > > >
Re: [VOTE] Enable github issue
+1 —— 毛东方 maod...@mails.tsinghua.edu.cn
Re: [VOTE] Enable github issue
+1 Best Regards, — Tianan Li School of Software, Tsinghua University 李天安 清华大学 软件学院 > 2020年1月3日 下午5:33，Jialin Qiao 写道： > > Hi, > > I'd like to call a vote for enabling github issue. > > The github issues could be treated as user mail list because Chinese users > prefer github issue more than Jira. However, for more convenient project > management consideration, we also use Jira. > > We could manage github and jira as follows: > > 【Create GitHub issue】Users create github issues when they want to report a > bug or new feature. Discussion is performed under github issues. > > 【Create Jira issue】 If a github issue is valuable, we create a Jira issue > for it and link the github issue url. After that, we add a [IOTDB-xxx] > prefix in the title of github issue to mark it is already related to a Jira > issue. > > 【Create PR】 Each functional PR or bug-fix PR should relate to a Jira issue. > PMCs or committers could help link PR with Jira issues. Some minor PRs > could be merged without a link to Jira issues, such as fix a typo. > > 【Close Jira Issue、Close github Issue、Merge PR】 Before mergine a PR, the > contributor or the one merges the PR should mark the fixed-version in Jira > issue and close the github issue if it is related. > > The vote is open for the next 72 hours and passes if at least three +1 > votes and more +1 votes than -1 votes. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Best, > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
??????[VOTE] Enable github issue
Hi~ That's an amazing idea, +1 for github issue +0 for still using jira Best Regards, Kaifeng Xue ------ ??:"Jialin Qiao" :2020??1??3?? ?? 5:33 ??:"dev" :[VOTE] Enable github issue Hi, I'd like to call a vote for enabling github issue. The github issues could be treated as user mail list because Chinese users prefer github issue more than Jira. However, for more convenient project management consideration, we also use Jira. We could manage github and jira as follows: ??Create GitHub issue??Users create github issues when they want to report a bug or new feature. Discussion is performed under github issues. ??Create Jira issue?? If a github issue is valuable, we create a Jira issue for it and link the github issue url. After that, we add a [IOTDB-xxx] prefix in the title of github issue to mark it is already related to a Jira issue. ??Create PR?? Each functional PR or bug-fix PR should relate to a Jira issue. PMCs or committers could help link PR with Jira issues. Some minor PRs could be merged without a link to Jira issues, such as fix a typo. ??Close Jira Issue??Close github Issue??Merge PR?? Before mergine a PR, the contributor or the one merges the PR should mark the fixed-version in Jira issue and close the github issue if it is related. The vote is open for the next 72 hours and passes if at least three +1 votes and more +1 votes than -1 votes. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Best, -- Jialin Qiao School of Software, Tsinghua University ?? ??
Re: [VOTE] Enable github issue
+1 On Fri, Jan 3, 2020 at 5:48 PM atoiLiu wrote: > Hi， > +1 > Regards, > > > 在 2020年1月3日，下午5:33，Jialin Qiao 写道： > > > > Hi, > > > > I'd like to call a vote for enabling github issue. > > > > The github issues could be treated as user mail list because Chinese > users > > prefer github issue more than Jira. However, for more convenient project > > management consideration, we also use Jira. > > > > We could manage github and jira as follows: > > > > 【Create GitHub issue】Users create github issues when they want to report > a > > bug or new feature. Discussion is performed under github issues. > > > > 【Create Jira issue】 If a github issue is valuable, we create a Jira issue > > for it and link the github issue url. After that, we add a [IOTDB-xxx] > > prefix in the title of github issue to mark it is already related to a > Jira > > issue. > > > > 【Create PR】 Each functional PR or bug-fix PR should relate to a Jira > issue. > > PMCs or committers could help link PR with Jira issues. Some minor PRs > > could be merged without a link to Jira issues, such as fix a typo. > > > > 【Close Jira Issue、Close github Issue、Merge PR】 Before mergine a PR, the > > contributor or the one merges the PR should mark the fixed-version in > Jira > > issue and close the github issue if it is related. > > > > The vote is open for the next 72 hours and passes if at least three +1 > > votes and more +1 votes than -1 votes. > > > > Please vote accordingly: > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Best, > > -- > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > >
Re: [VOTE] Enable github issue
Hi， +1 Regards, > 在 2020年1月3日，下午5:33，Jialin Qiao 写道： > > Hi, > > I'd like to call a vote for enabling github issue. > > The github issues could be treated as user mail list because Chinese users > prefer github issue more than Jira. However, for more convenient project > management consideration, we also use Jira. > > We could manage github and jira as follows: > > 【Create GitHub issue】Users create github issues when they want to report a > bug or new feature. Discussion is performed under github issues. > > 【Create Jira issue】 If a github issue is valuable, we create a Jira issue > for it and link the github issue url. After that, we add a [IOTDB-xxx] > prefix in the title of github issue to mark it is already related to a Jira > issue. > > 【Create PR】 Each functional PR or bug-fix PR should relate to a Jira issue. > PMCs or committers could help link PR with Jira issues. Some minor PRs > could be merged without a link to Jira issues, such as fix a typo. > > 【Close Jira Issue、Close github Issue、Merge PR】 Before mergine a PR, the > contributor or the one merges the PR should mark the fixed-version in Jira > issue and close the github issue if it is related. > > The vote is open for the next 72 hours and passes if at least three +1 > votes and more +1 votes than -1 votes. > > Please vote accordingly: > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Best, > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院
Re: [DISCUSS] Enable github issue?
> and it should clearly describe how we work after opening issue absolutely +1 --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 atoiLiu 于2020年1月3日周五 下午4:55写道： > Hi， > I agree with Lei Rui opinion, and it should clearly describe how we work > after opening issue > > Regards， > > > > 在 2020年1月3日，下午4:49，Lei Rui 写道： > > > > I would suggest a formal vote. > > > > > > Regards, > > Lei Rui > > > > > > On 1/3/2020 16:41，Jialin Qiao wrote： > > Hi, > > > > In the discussion about enabling github issues, 5 people support while no > > other voices. > > > > Jialin Qiao > > Minhao Gouwang > > Xiangdong Huang > > Tianci Zhu > > Dawei Liu > > > > I think there is no need to call for a vote. Meanwhile, Jira is also used > > and we could carry the issues to Jira through some tools. > > > > Could someone help enable the github issues? > > > > Thanks, > > > > Jialin Qiao 于2020年1月2日周四 下午4:29写道： > > > > Hi, > > > > Let's continue this discussion or make a decision? > > > > Jialin Qiao 于2019年12月31日周二 下午7:28写道： > > > > Hi, > > > > +1 for managing issues in github. > > +0 for using Jira. > > > > Thanks > > Jialin Qiao > > > > > > > > -- > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > > > > > > > -- > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > >
[VOTE] Enable github issue
Hi, I'd like to call a vote for enabling github issue. The github issues could be treated as user mail list because Chinese users prefer github issue more than Jira. However, for more convenient project management consideration, we also use Jira. We could manage github and jira as follows: 【Create GitHub issue】Users create github issues when they want to report a bug or new feature. Discussion is performed under github issues. 【Create Jira issue】 If a github issue is valuable, we create a Jira issue for it and link the github issue url. After that, we add a [IOTDB-xxx] prefix in the title of github issue to mark it is already related to a Jira issue. 【Create PR】 Each functional PR or bug-fix PR should relate to a Jira issue. PMCs or committers could help link PR with Jira issues. Some minor PRs could be merged without a link to Jira issues, such as fix a typo. 【Close Jira Issue、Close github Issue、Merge PR】 Before mergine a PR, the contributor or the one merges the PR should mark the fixed-version in Jira issue and close the github issue if it is related. The vote is open for the next 72 hours and passes if at least three +1 votes and more +1 votes than -1 votes. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: [DISCUSS] Enable github issue?
Hi， I agree with Lei Rui opinion, and it should clearly describe how we work after opening issue Regards， > 在 2020年1月3日，下午4:49，Lei Rui 写道： > > I would suggest a formal vote. > > > Regards, > Lei Rui > > > On 1/3/2020 16:41，Jialin Qiao wrote： > Hi, > > In the discussion about enabling github issues, 5 people support while no > other voices. > > Jialin Qiao > Minhao Gouwang > Xiangdong Huang > Tianci Zhu > Dawei Liu > > I think there is no need to call for a vote. Meanwhile, Jira is also used > and we could carry the issues to Jira through some tools. > > Could someone help enable the github issues? > > Thanks, > > Jialin Qiao 于2020年1月2日周四 下午4:29写道： > > Hi, > > Let's continue this discussion or make a decision? > > Jialin Qiao 于2019年12月31日周二 下午7:28写道： > > Hi, > > +1 for managing issues in github. > +0 for using Jira. > > Thanks > Jialin Qiao > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院
Re: [DISCUSS] Enable github issue?
I would suggest a formal vote. Regards, Lei Rui On 1/3/2020 16:41，Jialin Qiao wrote： Hi, In the discussion about enabling github issues, 5 people support while no other voices. Jialin Qiao Minhao Gouwang Xiangdong Huang Tianci Zhu Dawei Liu I think there is no need to call for a vote. Meanwhile, Jira is also used and we could carry the issues to Jira through some tools. Could someone help enable the github issues? Thanks, Jialin Qiao 于2020年1月2日周四 下午4:29写道： Hi, Let's continue this discussion or make a decision? Jialin Qiao 于2019年12月31日周二 下午7:28写道： Hi, +1 for managing issues in github. +0 for using Jira. Thanks Jialin Qiao -- — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 -- — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: [DISCUSS] Apache IoTDB (incubating) 0.9.1 RC1
@jincheng sun Thanks for your kind sharing. Regards, Lei Rui On 1/3/2020 16:01，jincheng sun wrote： I see. Thanks for your feedback! Lei Rui & Justin! As I know, Both Apache Beam[1] and Apache Flink[2] carry website updated PRs when bring up the release votes. This approach benefits Apache Beam and Apache Flink as the update changes of Beam and Flink are a little more complicated compare with Apache IoTDB, this approach speeds up the entire publishing process. However, the current update of the IoTDB website is a little bit easy, So, this approach has not brought obvious benefits. So, I am fine with keep current process of IoTDB. [1] https://lists.apache.org/thread.html/2fa0dd0e8710e62deab2e25c6081ed94636448f123d6f91ad190aa21%40%3Cdev.beam.apache.org%3E [2] https://lists.apache.org/thread.html/716337faba0160e8382543c8eb10bfa34895efc2419e94a1f3cc8d19%40%3Cdev.flink.apache.org%3E Best, Jincheng Lei Rui 于2020年1月3日周五 下午2:06写道： Hi, No need +1. I don't think it's a good practice, because if the released file doesn't exist, how can people review a PR like [1] where there are download links in it waiting to be checked, e.g., https://www.apache.org/dyn/closer.cgi/incubator/iotdb/0.9.0-incubating/apache-iotdb-0.9.0-incubating-source-release.zip . Regards, Lei Rui [1] https://github.com/apache/incubator-iotdb-website/commit/dc4d0226985c976561944068fd012e5cdfab4339 On 1/3/2020 13:52，jincheng sun wrote： No. You should only update the website after the IPMC vote has passes, the file put into the Apache mirrors and you waited 24 hours or so for the release to propagate. I mean that prepare the PR when bring up the VOTE, then people can review the PR ASAP. we can merge it when vote has passed and 24 hours later after the release . Best, Jincheng Lei Rui 于2020年1月3日周五 下午12:22写道： Thank Justin for the quick reply. Regards, Lei Rui On 1/3/2020 11:43，Justin Mclean wrote： Hi, Do you think that when bring up a release VOTE, we need to add the PR of update the website in VOTE thread? The changes of the PR would be similar with No. You should only update the website after the IPMC vote has passes, the file put into the Apache mirrors and you waited 24 hours or so for the release to propagate. Thanks, Justin
Re: [DISCUSS] Apache IoTDB (incubating) 0.9.1 RC1
I see. Thanks for your feedback! Lei Rui & Justin! As I know, Both Apache Beam[1] and Apache Flink[2] carry website updated PRs when bring up the release votes. This approach benefits Apache Beam and Apache Flink as the update changes of Beam and Flink are a little more complicated compare with Apache IoTDB, this approach speeds up the entire publishing process. However, the current update of the IoTDB website is a little bit easy, So, this approach has not brought obvious benefits. So, I am fine with keep current process of IoTDB. [1] https://lists.apache.org/thread.html/2fa0dd0e8710e62deab2e25c6081ed94636448f123d6f91ad190aa21%40%3Cdev.beam.apache.org%3E [2] https://lists.apache.org/thread.html/716337faba0160e8382543c8eb10bfa34895efc2419e94a1f3cc8d19%40%3Cdev.flink.apache.org%3E Best, Jincheng Lei Rui 于2020年1月3日周五 下午2:06写道： > Hi, > > > No need +1. > > > I don't think it's a good practice, because if the released file doesn't > exist, how can people review a PR like [1] where > there are download links in it waiting to be checked, e.g., > > https://www.apache.org/dyn/closer.cgi/incubator/iotdb/0.9.0-incubating/apache-iotdb-0.9.0-incubating-source-release.zip > . > > > Regards, > Lei Rui > > > [1] > https://github.com/apache/incubator-iotdb-website/commit/dc4d0226985c976561944068fd012e5cdfab4339 > On 1/3/2020 13:52，jincheng sun wrote： > No. You should only update the website after the IPMC vote has passes, > the file put into the Apache mirrors and you waited 24 hours or so for the > release to propagate. > > I mean that prepare the PR when bring up the VOTE, then people can review > the PR ASAP. we can merge it when vote has passed and 24 hours later after > the release . > > Best, > Jincheng > > > > Lei Rui 于2020年1月3日周五 下午12:22写道： > > Thank Justin for the quick reply. > > > Regards, > Lei Rui > On 1/3/2020 11:43，Justin Mclean wrote： > Hi, > > Do you think that when bring up a release VOTE, we need to add the PR of > update the website in VOTE thread? The changes of the PR would be similar > with > > No. You should only update the website after the IPMC vote has passes, the > file put into the Apache mirrors and you waited 24 hours or so for the > release to propagate. > > Thanks, > Justin >
