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 <[email protected]> Date: Sun,Mar 10,2019 11:48 AM To: dev <[email protected]> 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 <[email protected]> ??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 > > ?1?3Am 09.03.19, 11:48 schrieb "Justin Mclean" <[email protected]>: > > 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 > >
