I think it would be rather good to keep a 'release notes' document that is updated as new changes are done, merged to release branch during release process, and then becomes part of new release. Am I right that we don't have such a document right now, or I'm missing something? - Volodya
On 09/04/2008, Vladimir Prus <ghost@cs.msu.su> wrote:
I think it would be rather good to keep a 'release notes' document that is updated as new changes are done, merged to release branch during release process, and then becomes part of new release.
Am I right that we don't have such a document right now, or I'm missing something?
No we don't. It's a good idea though. A possible alternative would be if individual libraries and tools had a changelog as part of their documentation. That would also be easier to maintain when merging with release (since some changes in trunk might not make it into the release), and could be more detailed than the release notes. Daniel
On Apr 9, 2008, at 12:00 PM, Vladimir Prus wrote:
I think it would be rather good to keep a 'release notes' document that is updated as new changes are done, merged to release branch during release process, and then becomes part of new release.
Am I right that we don't have such a document right now, or I'm missing something?
We used to do that (or were supposed to do that) with the top-level index.htm, but it wasn't exactly a great system. - Doug
participants (3)
-
Daniel James -
Doug Gregor -
Vladimir Prus