You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Noah Slater (JIRA)" <ji...@apache.org> on 2012/09/29 17:28:07 UTC

[jira] [Created] (COUCHDB-1542) Share content from 1.1 in main docs somehow (ssl, proxying)

Noah Slater created COUCHDB-1542:
------------------------------------

             Summary: Share content from 1.1 in main docs somehow (ssl, proxying)
                 Key: COUCHDB-1542
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1542
             Project: CouchDB
          Issue Type: Task
          Components: Documentation
            Reporter: Noah Slater


Taken from the TODO.txt file after initial docs import.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (COUCHDB-1542) Share content from 1.1 in main docs somehow (ssl, proxying)

Posted by "Dave Cottlehuber (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COUCHDB-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Cottlehuber closed COUCHDB-1542.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3
         Assignee: Dave Cottlehuber

Done - required moving all the 1.1 features.rst content into other docs.
                
> Share content from 1.1 in main docs somehow (ssl, proxying)
> -----------------------------------------------------------
>
>                 Key: COUCHDB-1542
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1542
>             Project: CouchDB
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Noah Slater
>            Assignee: Dave Cottlehuber
>             Fix For: 1.3
>
>
> Taken from the TODO.txt file after initial docs import.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira