You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@brooklyn.apache.org by drigodwin <gi...@git.apache.org> on 2017/04/12 22:33:27 UTC

[GitHub] brooklyn-docs pull request #168: Refactor blueprinting

GitHub user drigodwin opened a pull request:

    https://github.com/apache/brooklyn-docs/pull/168

    Refactor blueprinting

    This PR refactors blueprints in the following way:
    * Renames YAML blueprints to writing blueprints and makes it the main focus
    * Moves Java blueprints inside writing blueprints
    * Moves YAML catalog reference inside writing blueprints
    * Re-orders a lot of the menus
    * Renames operations, reference guide
    * Renames locations, Deploying Blueprints


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/drigodwin/brooklyn-docs refactor-blueprinting

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-docs/pull/168.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #168
    
----
commit f38b9e7bbcf745fdb6eb2526a334d26fd03cecfb
Author: Duncan Godwin <du...@cloudsoftcorp.com>
Date:   2017-04-12T17:02:16Z

    Refactor Blueprinting

commit 00f3096b49d5c59c0ed530c27ff8adc4ce23f5e1
Author: drigodwin <dr...@googlemail.com>
Date:   2017-04-12T22:29:21Z

    Remove split files

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #168: Refactor blueprinting

Posted by murdoaird <gi...@git.apache.org>.

Github user murdoaird commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/168
  
    Changes look good - helps readability of the docs site.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs issue #168: Refactor blueprinting

Posted by tbouron <gi...@git.apache.org>.

Github user tbouron commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/168
  
    Thanks @drigodwin, this looks really good indeed, it's easier to navigate through.
    
    LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] brooklyn-docs pull request #168: Refactor blueprinting

Posted by asfgit <gi...@git.apache.org>.

Github user asfgit closed the pull request at:

    https://github.com/apache/brooklyn-docs/pull/168


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---