[
https://issues.apache.org/jira/browse/COUCHDB-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648527#comment-13648527
]
Danish Muneer commented on COUCHDB-1787:
----------------------------------------
Thank you Dave for such a detailed insight, yes I understand now the
complexities, yes sure I will be applying in a GSoC manner after reading more
about Sphinx. One more thing, Friday is 3rd May, 5th May is Sunday. What's the
due date?
> 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
