r14935 - gnucash/branches/2.0 - update to release 2.0.2
Chris Lyttle
chris at wilddev.net
Sun Oct 8 15:54:55 EDT 2006
Yes, I missed his email until after I was done with the release. IMHO I
would rather not see bug #'s in release announcements, if people want to
refer to a bug then they should look in the changelog. To me both the
NEWS and announcement notes should be geared towards something a user
would be interested in hearing about, such as UI changes, crasher fixes,
etc. Things such as;
Do not printf(%s,NULL) on Solaris
Drop gtktreedatalist because it conflicts with the gtk+ version
really shouldn't be there as most users wont have a clue what they mean.
Having said that, I will definitely incorporate some of what's there
into the announcement.
Chris
Christian Stimming wrote:
> Am Sonntag, 8. Oktober 2006 18:55 schrieb Chris Lyttle:
>
>> Author: wilddev
>> Date: 2006-10-08 12:55:17 -0400 (Sun, 08 Oct 2006)
>> New Revision: 14935
>> Trac: http://svn.gnucash.org/trac/changeset/14935
>>
>> Modified:
>> gnucash/branches/2.0/ChangeLog
>> gnucash/branches/2.0/NEWS
>> gnucash/branches/2.0/configure.in
>> Log:
>> update to release 2.0.2
>>
>
> Thanks for the updating for the release.
>
> However, regarding the NEWS text I was wondering whether you have taken
> http://wiki.gnucash.org/wiki/Announcement_2.0.2 into account? It didn't seem
> so when checking your commit. Andi has already written up a useful collection
> of those bugs that have been fixed and/or improved. The final announcement
> (on -announce) should use the text from the wiki as well.
>
> Thanks a lot,
>
> Christian
>
>
More information about the gnucash-devel
mailing list