@bismy, Can you give us the link for the document? We can update the website for these versioned documents.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 8, 2018 at 9:28 AM, bismy <[email protected]> wrote: > Yes. We have to build a release version of doc. And documents can give > link to versions. > e.g. > Java chassis document > latest > 1.1.0 > 1.0.0 > > > > > ------------------ 原始邮件 ------------------ > 发件人: "willem.jiang"<[email protected]>; > 发送时间: 2018年8月7日(星期二) 晚上10:15 > 收件人: "dev"<[email protected]>; > > 主题: Re: [DISCUSS]Add separated selectable version to our documents > > > > As the gitbook is using git , we should to the release just as we do for > the source code. > > But the challenge is how we host the gitbook, maybe we add the gitbook > build as part of our release process. > > Any thought? > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Aug 7, 2018 at 9:30 AM, 郑扬勇 <[email protected]> wrote: > > > Hi, all: > > We had implement many new features step by step in each release, so I > > think we also need make docs with separated version like : > > > > -------------------------------------------- > > User guide version : 1.0.0 ↓ > > -------------------------------------------- > > > > document content ... > > > > > > > > -------------------------------------------- > > > > Then user can clear known any feature in which version implemented, > Any > > thoughts ? > > > > Best Regards & Thanks > > YangYongZheng >
