Hi, I agree with Willem. PRs should generally go to master (develop, see discussion below).
If we discuss that one Patch is so important that we want to create a "hotfix" release than we will pick it to the "rel/0.8" branch and do a new release there (tagget then 'release/0.8.1' for example). But I think in this case its better to first start the discussion for a release before starting to cherry-pick or something. Julian Am 21.08.19, 11:00 schrieb "Willem Jiang" <[email protected]>: If you want to provide patch release, you need to create a branch 0.8.x once you cut the 0.8.0. For the bug fix, you need to commit the change to master branch and then back port it from master to 0.8.x. My suggestion is you just send PR to master and then do the cherry pick in your local 0.8.x branch and then send a PR to 0.8.x branch. As JIRA support multiple versions, you need to update the fix version once the PR is merged into different branch. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 21, 2019 at 4:50 PM Xiangdong Huang <[email protected]> wrote: > > Hi, > > v0.8.0 is released, and the IoTDB project is keeping developing. > > I think it is no dispute that putting new features into v0.9.0 or other > future version. > > The question is, do we have plan to release bug-fix versions, i.e., v0.8.1, > v0.8.2, etc.. And if so, which branch should the related PR be merged > (rel/0.8?) > > For example, PR#347 (thank Lei Rui catching it) is a critical bug for a > database (in my opinion). So, do we need to release a bug-fixed version on > v0.8.0 (e.g., after fixing 10 bugs, we can release a minor version). > > By the way, as we have released versions now, please record iotdb's version > when you record issues on JIRA, and add the solved versions when the issue > is closed. > > Best, > > > > > -- > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院
