couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2241) Add release dates to release history
Date Mon, 16 Jun 2014 20:26:03 GMT

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

Alexander Shorin commented on COUCHDB-2241:
-------------------------------------------

> I didn't know the precise release procedure for CouchDB and I did not talk about any
tarballs. So any doc changes require a voting process?

No, any changes in release tarball requires for new vote round and this shifts release date
for unknown period. 
The problem with just fixing docs manually and post factum I already noted: docs in tarballs
will not have information about own release date leaving this issue actual.

> Add release dates to release history
> ------------------------------------
>
>                 Key: COUCHDB-2241
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2241
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Documentation
>            Reporter: Jan-Erik
>
> The current release history listing at http://couchdb.readthedocs.org/en/latest/whatsnew/
does not include dates per version.
> It is always nice to have exact dates when a certain version was released. I suggest
from now on adding dates when a new version is added.
> It should also be noted that 1.6 is not yet released as stable. If someone finds some
time adding dates to old releases would be nice as well.
> Also your current release support policy from http://wiki.apache.org/couchdb/CurrentReleases
should be migrated to the new docs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message