couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Shorin <>
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 07:00:41 GMT
Hi Dave!

> What I mean is that instead of having in the source tree:
> release.1.4.rst
> release.1.3.1.rst
> releaseā€¦. etc
> we just have release.rst, and if you want to see the release notes for
> a specific (historic) version you'll just checkout that branch, or
> link to it directly in the ASF web-browsable repo.

This is bad idea by two reasons:

0. Namespaces are good. Placing all this stuff under release/
directory removes top level pollution.
1. For every new release there is need to copy-paste old release.rst
to release.{version}.rst - that is boring and erroneousness. Naming
them explicitly like 1.3.rst removes this problem from start.
2. Showing version number in url helps to figure to which CouchDB
version this release notes are belongs to. Just release.rst is about
something unspecific.

The use case I'm referencing to is Python docs:

> Alex, I also agree having a single file with the history in it for
> release notes is a Good Thing albeit more work. I can't think of a
> better (less work) way that still makes it easy for users.
> Seems we are all in agreement now, how about I summarise this up later
> today (unless somebody beats be to it) and we start working through
> this for 1.3.1 ?

Not agreed by reasons above. Probably I'll make some demo to show.

> Alex/Dirkjan - have you any more outstanding doc bits to merge in? We
> also have Stefan's github PR
> to go in.

I'd take this changes as modified patch into my local repo since I
have a bit different docs structure now. They are not forgotten.


View raw message