[ 
https://issues.apache.org/jira/browse/TINKERPOP3-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978080#comment-14978080
 ] 

ASF GitHub Bot commented on TINKERPOP3-922:
-------------------------------------------

GitHub user spmallette opened a pull request:

    https://github.com/apache/incubator-tinkerpop/pull/124

    TINKERPOP3-922 Created developer book.

    https://issues.apache.org/jira/browse/TINKERPOP3-922
    
    Moved CONTRIBUTING and RELEASE to the developer book.  Docs seem to publish 
fine with this change.  Here are the developer docs on 3.1.0-SNAPSHOT:
    
    http://tinkerpop.incubator.apache.org/docs/3.1.0-SNAPSHOT/developer.html

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

    $ git pull https://github.com/apache/incubator-tinkerpop TINKERPOP3-922

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

    https://github.com/apache/incubator-tinkerpop/pull/124.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 #124
    
----
commit 3a3fdf751263036fa0974bfc1f6da8e4faba8ddc
Author: Stephen Mallette <[email protected]>
Date:   2015-10-27T21:28:39Z

    TINKERPOP3-922 Created developer book.
    
    Moved CONTRIBUTING and RELEASE to the developer book.

----


> Add a book for Developer Documentation
> --------------------------------------
>
>                 Key: TINKERPOP3-922
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-922
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 3.0.2-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>             Fix For: 3.1.0-incubating
>
>
> Merge the RELEASE and CONTRIBUTING docs into this new book.  Keep 
> CONTRIBUTING around with content that points to the developer docs as the new 
> source for that stuff.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to