[jira] [Commented] (LIBCLOUD-620) Exception Class Hierarchy Lost with Move to Readthedocs

["Tomaz Muraus (JIRA)" <ji...@apache.org>]

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

Tomaz Muraus commented on LIBCLOUD-620:
---------------------------------------

API documentation for all the versions should still be available at - http://libcloud.apache.org/apidocs/

Currently this process is manual and it appears we forgot to do that for the past couple of release. I will work on back-filling API docs with missing versions and figure out if we can some how hook it to our build pipeline.

> Exception Class Hierarchy Lost with Move to Readthedocs
> -------------------------------------------------------
>
>                 Key: LIBCLOUD-620
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-620
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 0.14.0-beta3
>            Reporter: Will Bond
>            Priority: Minor
>
> I am starting to work with libcloud and trying to write my code in a robust way to handle connection issues. Unfortunately there doesn't seem to be any documentation about exceptions, especially at the connection layer.
> It seems there used to be with old versions. For example: http://libcloud.apache.org/apidocs/0.13.2/classIndex.html. From what I can tell, starting with version 0.14.0 and the move to readthedocs, there is is no longer a way to get this info without reading the whole codebase.
> It would be really useful to provide something like this moving forward.



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