couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amarnath Beedimane Hanumantharaya (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1787) Automate release process documentation
Date Wed, 18 Mar 2015 20:37:38 GMT


Amarnath Beedimane Hanumantharaya commented on COUCHDB-1787:

my name is Amarnath Beedimane Hanumantharaya am a master student at University of Missouri-
Kansas city.can i take up this project since i have a prior experience of Working as Quality
Engineer in SAP Labs India Pvt Ltd.I was responsible for maintaining, modifying, creating
and monitoring process chains and recording, modifying scripts as and when the new scenario
arrived. I was also involved in unit testing and regression testing.and i have intermediate
skill in Python.

> Automate release process documentation
> --------------------------------------
>                 Key: COUCHDB-1787
>                 URL:
>             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
website and ) 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

View raw message