Re: KMail 2: problems after recent changes in unstable
Am Sonntag, 21. Juli 2013, 02:45:37 schrieb Shai Berger:
> Hi,
>
> In view of this and several other problems reported on this package, I
> believe it is not ready for "testing" yet.
>
> I know some of the reported problems (though, as far as I'm aware, not the
> major ones) have been solved in upstream; but pending the solution of
> others, this is only almost usable. That is, it can be used to read and
> write mail, but major workflows are broken to different degrees of
> annoyance.
>
> KDE team: If you can share pointers on how to help make this better (other
> than help upstream, of course), please do.
>
> But until it does get better, please avoid promoting it.
What do you mean by that?
At some time KDE SC 4.10 had to enter unstable. And I think its better to do
it now, rather than later in the development cycle of Jessie.
I do think that KDEPIM 2 still needs more stabilization and robustness work,
but I also think is would rather unwise to goal at shipping Jessie with KDEPIM
1 still which is unsupported from upstream.
That said, KMail 2 via POP3 even basically works for me now, using some
annoying work-arounds, but actually it does work for me. KMail 2 via IMAP for
company mail does to hang occassionally at retrieving folder contents forever,
for KMail 2 on workstation inside company network I cannot say much, cause
only recently upgraded. Other than having two kmails running at the same
perdition-proxied IMAP account tends to create crashing akonadi_imap resources
and log spam. All of these reported.
And that is what I think is important:
Report upstream, even though Kevin reads the list: A mailing list posting is
not an easily trackable bug report.
So I think whats important to make it better is:
1) Use it (if you can bear it).
2) Report bugs and really try to find clear and easy reproducers. I know that
can be tough, but except for becoming a KDEPIM dev yourself, I think thats the
most effective way forward.
I still think KDEPIM upstream would benefit from more developer time. I now
some of my more complex bugreports sitting there for ages without a response.
So maybe helping with some bug-triaging, maybe there will be an event again,
is likely also going to help.
For now I agree though that KDEPIM 2 is not still not suitable for stable yet.
To many robustness issues still floating around. I remember lots of bugs during
my migration period.
And there is still no clear, workable and end user friendly migration path.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: