Hi all, If you ask me I would do something different:
- create "develop" branch from the current head of "master" and make that the default branch. - update "master" to be identical with the latest release version (so in your case the 0.8.0 and not 0.8.1-SNAPSHOT) ... merge the release tagged revision to master. Chris Am 03.09.19, 10:24 schrieb "Boris Zhu" <[email protected]>: Hi, Agree with you. Best, Boris Zhu On Tue, Sep 3, 2019 at 4:15 PM Jialin Qiao <[email protected]> wrote: > Hi, > > > > Our last release is 0.8.0, and we make a lot of changes in master (we > treat master as dev). > > Some users want to use the functions in master. However, when they request > the documents, I just can't give a URL to them, maybe it's better to open a > document for master in our website. > > Currently, we have 0.8.0 and latest documents in our website. We could > leave 0.8.0 as default branch and rename the latest to master. > > > What do you think? > > > Best, > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院
