On 2014.07.31 11:05, Cristian Oneț wrote:
Hi,
First of let me apologize for spamming the list with the information
resulted from going over our open bugs list. I know it was a lot of
information but if anyone wonders how is that possible all I can say
is that was the length of untouched issues we had.
A lot of them are now waiting for info and I managed to confirm a few
of them which means they are ready to be fixed.
There were some issues which were already solved by commits so I
would like everyone in the future before committing a fix check if
there's an open issue for it and if there is bind it to the commit.
Also there are some issues opened by developers (Allan I'm looking at
you) could the authors go trough them and reconfirm if those are
still valid?
It serves nobody to have a long pending list because it will only
cause issues which can be fixed now relatively easy to go missing in
the haystack. There were around 140 bugs (I'm not including wishes)
and now they are 67 of which between 10-20 can be fixed and closed.
We can do better than this, please help to make it happen :)
Regards,
Cristian
P.S: these are the bugs.kde.org filters that I use
KMyMoney bugs:
Product: kmymoney4
Status: UNCONFIRMED, CONFIRMED, ASSIGNED, REOPENED
Severity: critical, grave, major, crash, normal, minor
KMyMoney crashes:
Severity: critical, grave, major, crash
Product: kmymoney4
Status: UNCONFIRMED, CONFIRMED, ASSIGNED, REOPENED
KMyMoney wishes:
Status: UNCONFIRMED, CONFIRMED, ASSIGNED, REOPENED
Product: kmymoney4
Severity: wishlist
KMyMoney needsinfo:
Product: kmymoney4
Status: NEEDSINFO
I hate to ask this right after you spent so much time and effort on
this, but is there any point in also going through the kmymoney2 bugs
to 1) close them all out 2) see if any of them are worth bringing up to
kmymoney4 (probably not, but perhaps some wishlist items might still be
valid.)
Jack
_______________________________________________
KMyMoney-devel mailing list
KMyMoney-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmymoney-devel
