[Kde-pim] Re: (sysadmin work?)
Marc Deop
damnshock at gmail.com
Fri Feb 11 11:58:27 GMT 2011
On Friday 11 February 2011 10:38:44 Thomas McGuire wrote:
> There is actually a "KMail2" product. In retrospect, it would have been
> better to add that as a version to the "KMail"product instead, since
> having two products is apparently to confusing for reports.
Well, now that I think about it...makes sense as kmail2 is rewritten almost
from scratch (AFAIK). However, this brings the kind of situations we are
talking here.
> Maybe sysadmin can move all reports from KMail2 to KMail with version
> "2.0.89"?
Mmmm this is tricky. Many bug reports for kmail1 should move to akonadi if we
are talking about kmail2, but stay the same otherwise.
For example let's check https://bugs.kde.org/show_bug.cgi?id=67504
It's a wish for kmail to support imap. Well, kmail1 doesn't support it but
*akonadi* does (and so does Kmail2).
Therefore... should we move the wish to akonadi and mark it as "Resolved" or
should we leave it the same as kmail1 *is* responsible for imap?
My opinion is that if kmail1 is no longer developed, we should mark those bugs
as Solved in version 2.
What do you think of this guys? This might help to reduce the number of bugs
in kde and the work for the developers.
--
Regards,
Marc Deop
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
More information about the kde-pim
mailing list