couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amarnath Beedimane Hanumantharaya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1787) Automate release process documentation
Date Sat, 25 Apr 2015 18:03:38 GMT

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

Amarnath Beedimane Hanumantharaya commented on COUCHDB-1787:
------------------------------------------------------------

Hi Robert,
still now i didn't get confirmation of my proposal?



> 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: gsoc, gsoc2015, mentor
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message