brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ahgittin <...@git.apache.org>
Subject [GitHub] brooklyn-docs issue #185: [Suggestion] Merge guide/dev into website/develope...
Date Tue, 20 Jun 2017 12:07:59 GMT
Github user ahgittin commented on the issue:

    https://github.com/apache/brooklyn-docs/pull/185
  
    Do not merge yet.  In addition to the comments the case for making this change needs to
be made.
    
    The reason for the old docs structure is that some of the dev guide content is specific
to a given version.  We lose that clarity with this PR.  I expect @bostko is suggesting that
precision is not worth the user-facing complexity, but @bostko it would be helpful to describe
how this is simpler and note main places confusion could arise if we don't have the dev guide
aligned for released versions.


---
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.
---

Mime
View raw message