All, I think it's worth considering moving the fuel-dev docs from fuel-web to fuel-docs repository. The development docs are relevant for all our repositories, not just fuel-web, and it, given the similarities between fuel-docs and fuel-web/docs, will be easier to maintain a single set of CI scripts instead of maintaining two slightly different copies.
My 2c, -Dmitry On Mon, Dec 16, 2013 at 2:43 PM, Ivan Kolodyazhny <[email protected]> wrote: > Thanks Dmitry, it was my typo. > > Example of CI checks and docs preview: > Here is build for review request #6187 > https://fuel-jenkins.mirantis.com/job/stackforge-verify-fuel-docs/46/. "Fuel > Docs build results" link navigates you to a docs preview. > > We've got development documentation(docs.mirantis.com/fuel-dev/) in a > fuel-web repository. We have no any development docs checks or preview for > review requests but we are working on it. > > > On Tue, Dec 17, 2013 at 12:38 AM, Dmitry Borodaenko > <[email protected]> wrote: >> >> On Mon, Dec 16, 2013 at 2:23 PM, Ivan Kolodyazhny >> <[email protected]> wrote: >> > As was announced earlier, we moved our user and administration guide to >> > StackForge: https://github.com/stackforge/fuel-web. >> >> Actual link: https://github.com/stackforge/fuel-docs >> >> (fuel-web is our repository for Fuel UI, not the documentation) >> >> -- >> Dmitry Borodaenko > > > > > -- > Regards, > Ivan "e0ne" Kolodyazhny, > Software Engineer, Mirantis, Inc. -- Dmitry Borodaenko -- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
