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"<willem.ji...@gmail.com>; ????????: 2018??8??7??(??????) ????10:15 ??????: "dev"<dev@servicecomb.apache.org>; ????: 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, ?????? <342906...@qq.com> 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
