Hi Jialin, of course it is. Adding Jira is just a service to point readers (or people who did a jira) directly to the issue and detailed description. But if you look at early PLC4X releases, we basically had non issues at all __
Julian Am 16.07.19, 10:16 schrieb "Jialin Qiao" <[email protected]>: Hi Julian, I will submit the PR about updating RELEASE_NOTES to rel/0.8. Just one question, some PRs are not associated with Jira issues, is "listing them in the bottom of the corresponding list without a Jira number" ok? for example: Bug Fixes --------- IOTDB-7 OpenFileNumUtilTest failed fix time zone bug in different region (<---this one does not match a Jira issue) Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -----原始邮件----- > 发件人: "Julian Feinauer" <[email protected]> > 发送时间: 2019-07-16 15:50:15 (星期二) > 收件人: "[email protected]" <[email protected]> > 抄送: > 主题: Re: Volunteer as Release Manager for release 0.8 > > Hi all, > > so I created a release branch now called rel/0.8, see [1]. > Master branch is now set to the new development version 0.9.0-SNAPSHOT. > > This means, that all PRs should be rebased (which should be no problem in 99% of cases). > > So all changes we do regarding the release should go into rel/0.8. > If we fix bugs there they should be merged into rel/0.8 BUT also cherry-picked into master. > > @ Jialin: if you assist with the RELEASE_NOTES file you should do it in rel/0.8. > > So all PRs keep going to master and all future development and only things regarding the release will go into the rel/0.8 branch. > If we do major changes there they will be merged back to master regularily and we keep the branch open to support "minor" or "hotfix" releases. > > Best > Julian > > [1] https://github.com/apache/incubator-iotdb/tree/rel/0.8 > > Am 16.07.19, 09:43 schrieb "Julian Feinauer" <[email protected]>: > > Yes, I can spin up a release branch now and then everybody who does things for "release stabilization" should work there or point the PRs to there (like updating release notes and stuff). > > Am 16.07.19, 09:32 schrieb "Xiangdong Huang" <[email protected]>: > > Hi, > > So, do we need to confirm the source codes and create a release branch now? > > Best, > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer <[email protected]> 于2019年7月16日周二 下午12:54写道： > > > Hey Jialin, > > > > that is a very kind offer! > > Some time ago I already created a "RELEASE_NOTES" File (in the root) and > > added in what was there up till then. > > But as this was like 2 or 3 months ago it needs to be overworked. > > So feel free to extend the file. > > > > Julian > > > > Am 16.07.19, 04:32 schrieb "Jialin Qiao" <[email protected]>: > > > > Hi, > > > > It's very exciting that we are going to release the first version. > > > > PR #245, #232 have been merged successfully. Therefore, we could start > > to release. > > > > If needed, I will traverse the PRs and Issues to give a changes > > (major) list from 0.7.0 to 0.8.0. > > > > Best, > > -- > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > > > > -----原始邮件----- > > > 发件人: "Julian Feinauer" <[email protected]> > > > 发送时间: 2019-07-15 21:48:54 (星期一) > > > 收件人: "[email protected]" <[email protected]> > > > 抄送: > > > 主题: Re: Volunteer as Release Manager for release 0.8 > > > > > > Hey Xiangdong, > > > > > > I also think that the "changelog" will be huge. > > > But I'm unsure if we have to write everything as "change" because > > this is the "first" release with regards to the ASF so I'm unsure if we > > would point to 0.7 as "previous" release. > > > > > > @cdutz, @jmclean what is your point on that, how do other podlings > > handle that? > > > > > > Julian > > > > > > Am 15.07.19, 15:45 schrieb "Xiangdong Huang" <[email protected]>: > > > > > > Hi, > > > > > > Should we solve CVE problems in this release? > > > > > > Maven reports many CVE problem caused by dependencies... > > > > > > For example, > > > * Detected 1 vulnerable components: > > org.apache.thrift:libthrift:jar:0.9.3 > > > * Detected 1 vulnerable components: > > ch.qos.logback:logback-core:jar:1.1.11 > > > > > > It is easy to fix them by upgrading their version. However, > > current master > > > branch works in stable, and if we upgrade the version of > > dependencies, > > > maybe we need more time to test. > > > > > > Therefore, I'd like to ignore them in this release.... > > > > > > Best, > > > ----------------------------------- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > > > > > > > > Xiangdong Huang <[email protected]> 于2019年7月15日周一 下午9:26写道： > > > > > > > Hi, > > > > > > > > First, I think PR #245, #232 can go into 0.8. The codes have > > been > > > > reviewed and approved. Hope the authors can finish their tests > > and merge > > > > them tonight. > > > > > > > > There are many many changes comparing with 0.7. And, there are > > many data > > > > files and configurations that conflict with 0.7. We need to > > review recently > > > > issues and PRs to filter them out and form the Changes file. > > > > > > > > Best, > > > > ----------------------------------- > > > > Xiangdong Huang > > > > School of Software, Tsinghua University > > > > > > > > 黄向东 > > > > 清华大学 软件学院 > > > > > > > > > > > > Julian Feinauer <[email protected]> 于2019年7月15日周一 > > 下午8:46写道： > > > > > > > >> Hi all, > > > >> > > > >> first, thanks again to the PPMC to invite me as a Comitter. > > > >> As I have all necessary rights now I can hereby offer to do > > the release > > > >> manager for the release 0.8 which will be the first official > > ASF release of > > > >> IoTDB. > > > >> > > > >> As suggested in the other Thread, I think it would be good to > > start off > > > >> with the release soon just to learn the process together and > > do all > > > >> necessary checking and clearance. > > > >> For that I am very happy that we have Chris and Justin on the > > team who > > > >> are very experienced and sharp eyed. > > > >> > > > >> Are there any issues that you think should go into 0.8 > > (feature) wise > > > >> before spinning up a release branch? > > > >> I will also open a “Release” in jira, so that we can assign > > and track the > > > >> tickets there. > > > >> > > > >> Julian > > > >> > > > > > > > > > > > > > > > > > > > >
