[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Akonadi Meeting: exception request. / Porting Status?
From:       Jos Poortvliet <jospoortvliet () gmail ! com>
Date:       2010-05-10 16:11:24
Message-ID: AANLkTilFZZTFbvys1SmHQcJ-TONxDW-j__HVr5eYX4bB () mail ! gmail ! com
[Download RAW message or body]

On Mon, May 10, 2010 at 12:11 PM, Sebastian Kügler <sebas@kde.org> wrote:
> Hi PIMsters,

<snip>

> When would be a good moment to start testing KDE PIM 4.5? I've svn switched those
> modules to the 4.4 version until further notice when you guys began porting, but
> haven't seen any meaningful communication about stability and progress of this
> critical KDE SC component.

Yes, communication is lacking now. I'd love to see a little more
blogging and info for users, even a call for testing or help if there
are issues - let us know what is going on. Even if it's just a few
bullet points on a blog or a repost of an important mail to the pim
mailinglist... Doesn't have to be complicated.

And if there is or might be an issue, we should communicate it to our
users, rally some support in testing or even patches... You can't
expect 10 new developers in a week but by having regular updates
people will have more feeling with PIM and are more inclined to help
out.

If you need help with this, just let me know, the promo team is surely
willing to help but we need at least SOME input!

Cheers,
Jos

*A while ago there was a great plan to promote PIM better - will have
a look at that and see if I can start the discussion again.

> Thanks,
> --
> sebas
>
> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
> _______________________________________________
> release-team mailing list
> release-team@kde.org
> https://mail.kde.org/mailman/listinfo/release-team
>
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

[prev in list] [next in list] [prev in thread] [next in thread]