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

Danish Muneer commented on COUCHDB-1787:
----------------------------------------

I have worked in Python, and I am interested in doing this project. Can anyone 
give a more detailed approach to the issue, I am a student and could not figure 
out very clearly. I have understood that some documentations are needed to be 
extracted automatically using Python code and presented in a suitable manner 
for the release managers, making their work a bit easy. 

                
> Automate release process documentation
> --------------------------------------
>
>                 Key: COUCHDB-1787
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1787
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Build System, Documentation
>            Reporter: Dave Cottlehuber
>              Labels: gsoc2013, sphinx
>
> The release process today contains a large number of manual transformation 
> steps.
> Fixing this will make the release process significantly easier for release 
> managers, as well as less error-prone.
> Ideally the output formats (NEWS, CHANGES in source tree, and HTML snippets 
> for http://couchdb.org/ website and http://blogs.apache.org/couchdb ) can be 
> auto-generated from either the .rst files in share/doc/src using sphinx's 
> .versionaddded/changed tags, or potentially from commit messages if this is 
> appropriate.
> CouchDB documentation is generated today from restructured text using python 
> code, and rolled into the release documentation during `make distcheck`.

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

Reply via email to