yeah. I mean dubbo 2.x. but I also have a look at tomcat api doc( https://tomcat.apache.org/tomcat-8.5-doc/api/) maybe we can follow similar way. for example, for version 2.7.x, we have 2.7.1 and 2.7.2, we only publish version 2.7.2 under dubbo-2.7-doc folder.
On Mon, Jun 17, 2019 at 11:01 AM Huxing Zhang <hux...@apache.org> wrote: > Hi, > > On Sat, Jun 15, 2019 at 10:40 AM YunKun Huang <hty...@gmail.com> wrote: > > > > hey, > > > > The branch config change is done. And after two days testing for jenkins > > job, I turn off dryrun mode. > > > > Now all changes to dubbo-website will rebuild by CI, there may has some > > delay (changes may apply to website after a few hours.). > > > > If there is any change you want to made, please submit PR to master > branch. > > asf-site will handle by CI > > > > I also add a api-doc deployment job ( > > > https://builds.apache.org/job/Apache%20Dubbo/job/apache-dubbo-apidoc-deployment/ > ) > > which is required manual trigger with dubbo version param. > > Version 2.7.2 is ready at http://dubbo.apache.org/dubbo-2.0-doc/api/ > now. > > Great work! I have a minor question: > Why the url is http://dubbo.apache.org/dubbo-2.0-doc/api/? > If you mean dubbo 2.x, how about: > http://dubbo.apache.org/dubbo-2.x-doc/api/ ? > If you mean the latest stable version, how about > http://dubbo.apache.org/dubbo-2.7.2-doc/api/ ? > > > > > On Thu, Jun 13, 2019 at 9:03 PM YunKun Huang <hyun...@apache.org> wrote: > > > > > Now jenksin job is ready with dryrun mode: > > > > https://builds.apache.org/job/Apache%20Dubbo/job/apache-dubbo-website-deployment/64/console > > > > > > I'm going to asking help from Infra team to setup master branch as > default > > > branch for dubbo-website. > > > Once branch configuration is done, I will enable jenkins job and turn > on > > > automatic build for dubbo website > > > > > > On 2019/06/13 03:09:30, Yuhao Bi <byh0...@gmail.com> wrote: > > > > +1 > > > > good idea > > > > > > > > Huxing Zhang <hux...@apache.org> 于2019年6月13日周四 上午10:26写道： > > > > > > > > > Hi, > > > > > > > > > > On Wed, Jun 12, 2019 at 10:36 PM YunKun Huang <hty...@gmail.com> > > > wrote: > > > > > > > > > > > > hey, > > > > > > > > > > > > I'm working on a jenkins job to automaticlly generate website and > > > push > > > > > back > > > > > > to git repo. > > > > > > > > > > > > When I working on it, I noticed the dubbo-website only has one > active > > > > > > branch named 'asf-site'. > > > > > > > > > > > > The website is managed by a tool named 'docsite' which can > generate > > > > > website > > > > > > from source files. > > > > > > Currently for dubbo-website, all source files and generated files > > > are in > > > > > > same branch. it will cause some issue: > > > > > > > > > > > > 1.for user who want to contribute to website, he/she need clone > > > generated > > > > > > files togethere which is not nessary > > > > > > 2.people will confuse for which one need change, people may > create > > > PR to > > > > > > modify html which is generated and may overwite by docsite tool. > > > > > > 3.if we apply jenksin job to update website, the commit logs will > > > combine > > > > > > by jenkins automatic commit and other commits which is hard to > > > maintain. > > > > > > > > > > > > What i suggest is to use master branch to manage source files > which > > > > > accept > > > > > > PR and for asf-site branch, this is maintain by jenkins job. > > > > > > > > > > +1 to the proposal. > > > > > > > > > > > > > > > > > Camel website is using this strategy and looks like it works > well ( > > > > > > https://github.com/apache/camel-website) > > > > > > > > > > > > > > > > > > > > -- > > > > > Best Regards！ > > > > > Huxing > > > > > > > > > > > > > > > > -- > Best Regards！ > Huxing >
