Hi, Agree. I once wanted to maintain a branch called `dev`, so we can submit PRs to the `dev` branch, and then merge `dev` into `master`.. (actually `dev` branch exists on github repo now...)
But I find that it seems the branch does not have effect... Normally, If a PR pass all CI test (if the CI test is enough complete), then if we merge it into the master, we can guarantee the master is also stable.. So I do not maintain the dev branch anymore.. Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer <j.feina...@pragmaticminds.de> 于2019年3月10日周日 下午5:57写道： > Hi Chris, > > I think there is slight confusion. Currently iotdb has no develop and only > master branch where development happens. > Thus I suggest to create the file there (as done in my PR #91). > > Julian > > Von meinem Mobiltelefon gesendet > > > -------- Ursprüngliche Nachricht -------- > Betreff: Re: Do we have a plan to release the first normal version of > IoTDB this month? > Von: Christofer Dutz > An: dev@iotdb.apache.org > Cc: > > In other projects, we usually have release notes also in develop. Here we > have a section for the next planned version right at the top (but with an > "unreleased" appended to the version) and add stuff as it comes in. For a > release the "unreleased" is removed and merged to master, then a new entry > for the next version is added. > > Chris > > Outlook für Android<https://aka.ms/ghei36> herunterladen > > ________________________________ > From: 吴晟 Sheng Wu <wu.sh...@foxmail.com> > Sent: Sunday, March 10, 2019 4:53:00 AM > To: dev; dev > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > Hi. > > > Release note should be kept in master or further codes, I think. Users may > be interesting in the changes of old versions, in order to choose right > version. > And, make sense to create a new branch to do release, and versiob update. > You could make the version to 0.9.0-snapshot, after the release branch > created. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ------------------ Original ------------------ > From: Xiangdong Huang <saint...@gmail.com> > Date: Sun,Mar 10,2019 11:48 AM > To: dev <dev@iotdb.apache.org> > Subject: Re: Do we have a plan to release the first normal version of > IoTDB this month? > > > > Hi, > > Do we put this release note into the master branch, or create a new branch > called branch-0.8.0 and put this note into that branch? > (In the pom file of the master branch, the version is still > 0.8.0-SNAPSHOT) > > Best, > > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Julian Feinauer <j.feina...@pragmaticminds.de> 于2019年3月10日周日 上午4:07写道： > > > Hi all, > > > > I just prepared the initial version of the RELEASE_NOTES as PR in [1]. > > I just integrated all closed Jira issues. > > Now we should try to add all further (mentionable) improvements. > > Personally, I think this is not to crucial as this is the first apache > > release, so the question "what changed" or what changed incompatible is > not > > that crucial as for further releases. > > > > Best > > Julian > > > > https://github.com/apache/incubator-iotdb/pull/91 > > > > Am 09.03.19, 11:48 schrieb "Justin Mclean" <justinmcl...@me.com>: > > > > Hi, > > > > > In brief, there are four steps: (1) setting Maven configuration; > (2) > > > creating the release branch and prepare the codebase; (3) mvn > > release and > > > deploy and so on; (4) vote. > > > > You also need to check the LICENSE, NOTICE and DISCLAIMER files in > the > > release and we can help you with that. > > > > Thanks, > > Justin > > > > >
