Unexpected Cash Flow report behavior. Help?

[David Carlson]

On 11/26/2013 2:05 PM, Carsten Rinke wrote:
> Hi,
>
> I think this is what you need
> https://bugzilla.gnome.org/browse.cgi?product=GnuCash
>
> Judge yourself if you need this for download.
> The link is found on the GnuCash wiki page. So all information is
> available, maybe not in the format you prefer.
> But instead of reading every bug, it is maybe better to get familiar
> with the Wiki page and Bugzilla so you can search for specific faults
> once that you think you hit one.
>
> In the link below please note that only open bugs are listed.
> The cash flow miscalculation is not listed because it is not open
> anymore.
>
> Firefox has no issues?
> https://bugzilla.mozilla.org/buglist.cgi?f1=OP&f0=OP&o2=substring&f4=CP&query_format=advanced&j1=OR&f3=CP&f2=product&bug_status=NEW&v2=firefox&product=Firefox
>
>
> Kind regards,
> Carsten
>
>
Most of us are not ready to learn all the ins and outs of various bug
reporting systems, especially how to detect the fact that while "The
cash flow miscalculation is not listed because it is not open anymore. "
may be true, yet the bug remains in the current stable download. 

That is why a short list of known _serious_ bugs in the current stable
release on the download page would be very helpful. 

I think developers may get embarrassed if some bugs stay on the download
page for years, but perhaps that would be a good motivator to elevate
the priority to fix them.

David C
>
>
>
> On 11/26/2013 12:11 AM, David Carlson wrote:
>> On 11/25/2013 10:36 AM, ... wrote:
>>> It would be nice if there was a summary of the important problems
>>> with the
>>> version for download that was very clear and available.
>>>
>>> For instance, the bugzilla search for version 2.4.13 does not list
>>> the cash
>>> flow report issue.  Nor is it listed on the "report bugs" page you
>>> linked
>>> me to:
>>> https://bugzilla.gnome.org/buglist.cgi?product=GnuCash&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Reports
>>>
>>>
>>> As a user downloading the product, I would like to know what accounting
>>> related bugs I am working with.  It would be best if this was on the
>>> downloads page right next to the version to be downloaded, and
>>> included all
>>> errors present in that version that affect double entry accounting and
>>> reporting validity.  If the labels get cut off for being too long or
>>> there
>>> are other imperfections in the user interface, I know that's just
>>> part of a
>>> work in process.  If using an exchange rate breaks double entry
>>> accounting (
>>> https://bugzilla.gnome.org/show_bug.cgi?id=708941) or reports are
>>> giving
>>> untrue values, then users need to know about this.
>>>
>>> I really do appreciate all of your efforts and understand that I am
>>> relying
>>> on voluntary contributions.  I offer this suggestion as a suggestion to
>>> improve the utility of GNUCash to its users and increase our
>>> confidence in
>>> the product we are using.
>>>
>>> Thank you,
>>>    Elliot
>>>
>>>
>> This is a good point.  I just checked the FireFox Release notes page to
>> see how they do it.
>> <https://www.mozilla.org/en-US/firefox/25.0.1/releasenotes/>
>> Believe it or not, there currently are no listed "Known Issues" for
>> FireFox release 25.0.1, but if there were, they would be noted on
>> that page.
>> Per your comment GnuCash could do something similar.
>>
>> David C
>> _______________________________________________
>> gnucash-user mailing list
>> gnucash-user at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>
>