Re: What do we want from the Changelog?

2012-03-13 Thread Rudy Gevaert
Hello, I have a comment that (in my opinion) fits in this thread. I would like to see a good way of pointing out new imapd.conf options. Now you have to look at bug reports, changelog, install-upgrade to find them. Sometimes they are not documented even, but that is a different problem.

Re: What do we want from the Changelog?

2012-03-13 Thread Dave McMurtrie
On 03/13/2012 09:43 AM, Rudy Gevaert wrote: Hello, I have a comment that (in my opinion) fits in this thread. I would like to see a good way of pointing out new imapd.conf options. Now you have to look at bug reports, changelog, install-upgrade to find them. Sometimes they are not documented

What do we want from the Changelog?

2012-03-12 Thread Jeroen van Meeuwen (Kolab Systems)
Hi there, after my little screw-up not updating doc/changes.html, which has to happen manually, we're now in the realm of fixing this once and for all. We have the following sources for what changed: - git commit logs, - bugzilla entries, Sometimes, fixes are applied after one of our

Re: What do we want from the Changelog?

2012-03-12 Thread Dave McMurtrie
On Mar 12, 2012, at 5:33 PM, Bron Gondwana br...@fastmail.fm wrote: On Mon, Mar 12, 2012 at 09:27:55PM +, Jeroen van Meeuwen (Kolab Systems) wrote: Including those types of warnings and caveats will probably remain a manual process. I'm in favour of calling these Release Notes though,

Re: What do we want from the Changelog?

2012-03-12 Thread Bron Gondwana
On Mon, Mar 12, 2012 at 04:31:24PM -0700, Carson Gaspar wrote: On 3/12/12 2:39 PM, Dave McMurtrie wrote: We should probably remove the ChangeLog from the distribution (which will remove it from the online docs). We could then automate the ChangeLog from Git and make it only available online.