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

ASF GitHub Bot commented on GEODE-2777:
---------------------------------------

GitHub user karensmolermiller opened a pull request:

    https://github.com/apache/geode/pull/453

    GEODE-2777 Update docs to be for Geode version 1.2

    This PR only addresses doc changes in the Apache geode repository.  Any 
website changes related to releasing a 1.2 version of Geode will need to be 
done in a separate PR, and on the geode-site repository.
    
    @joeymcallister @davebarnes97 and any other Geode afficionados, will you 
please review this PR?

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

    $ git pull https://github.com/karensmolermiller/geode feature/GEODE-2777

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

    https://github.com/apache/geode/pull/453.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 #453
    
----
commit 152509797c437f1c7063d0583435d2f0d93b521f
Author: Karen Miller <kmil...@pivotal.io>
Date:   2017-04-13T17:17:21Z

    GEODE-2777 Update docs to be for Geode version 1.2

----


> Change version number from 1.1 to 1.2 in docs
> ---------------------------------------------
>
>                 Key: GEODE-2777
>                 URL: https://issues.apache.org/jira/browse/GEODE-2777
>             Project: Geode
>          Issue Type: Task
>          Components: docs
>            Reporter: Joey McAllister
>            Assignee: Karen Smoler Miller
>             Fix For: 1.2.0
>
>
> On the `develop` branch, change any reference to v1.1 to be v1.2 in the 
> `geode-docs` and `geode-book` directories.
> In the `geode-book` directory, make sure to change the hrefs in the subnav 
> from `/11/` to `/12/` and make relevant version changes to the `config.yml` 
> file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to