couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <kxe...@gmail.com>
Subject Re: [DISCUSS] How to generate our release notes (Was: Re: [4/6] git commit: updated refs/heads/1.3.x to 5e64395)
Date Tue, 21 May 2013 01:33:15 GMT
On Mon, May 20, 2013 at 5:16 PM, Dave Cottlehuber <dch@jsonified.com> wrote:
> I like this but we can just have a single release.rst file, and have git
> track changes. See what Alex already did with changes
>
>
> http://kxepal.iriscouch.com/docs/1.3/changelog.html

It's already in upstream (;
http://docs.couchdb.org/en/latest/changelog.html

However, may be better to split it by release e.g

share/doc/src/release/index.rst
share/doc/src/release/1.4/index.rst == Short brief about release:
goals, solutions, features etc.
share/doc/src/release/1.4/whatsnew.rst == NEWS
share/doc/src/release/1.4/changes.rst == CHANGES
share/doc/src/release/1.4/migration.rst == What if we break some back
compatibility?
share/doc/src/release/1.4/whatevermaybethere.rst == Reserved for future usage.

Any patch version bump include into since they doesn't brings anything
big and special (according semver) to have separate article.
Thoughts?


--
,,,^..^,,,

Mime
View raw message