KTp roadmap

Rohan Garg rohan16garg at gmail.com
Mon Feb 11 15:54:25 UTC 2013


Would it be possible to do a Beta release before 7th March? That way I
can ensure I can get KDE Telepathy in before the final 13.04 release
for Kubuntu.
www.launchpad.net/~rohangarg


On Sat, Feb 9, 2013 at 9:43 PM, David Edmundson
<david at davidedmundson.co.uk> wrote:
> On Mon, Feb 4, 2013 at 2:43 PM, David Edmundson
> <david at davidedmundson.co.uk> wrote:
>> KDE Telepathy Roadmap
>>
>> Hey all. The following is a summary of the discussions we had at FOSDEM.
>> Please comment if I've got something wrong, or if you weren't there.
>>
>> 0.5.3 release Next week
>>
>> =============
>>
>> Soft feature freeze Next week
>>
>> (i.e nothing that's not in the planned features list should be started)
>>
>> =============
>>
>> 0.6 release at the end of Q1:
>>
>> Things to note:
>>  - this will have run time optional _UNSTABLE_ kpeople. This will not be on
>> by default, and we do not encourage distros to package it in their main
>> repos
>>  - the API will NOT be considered ABI stable finished
>>
>> Big Features we want to have:
>>  - Completely finished model refactor (seems likely, things are going well)
>>  - Work on making the API as sane as possible, with doxygen documentation
>>  - merging _all_ of Lasath's plugins, with a message processor API that I'm
>> happy with (see RB)
>>  - Call UI with GStreamer 1.0 (gkiagia, could you forward a link to any
>> up-to-date QtGstreamer discussions)
>>  - Dan Vratil to relook into SASL handling
>>  - Less sucky notifications (d_ed to send separate email to the ML)
>>  - Show unread message icon in Contact List (see d_ed's branch of
>> contact-list)
>>  - Approver to handle all types of stream tubes thanks to .desktop files
>> describing the tubes.
>>
>> =============
>>
>> 0.7 release at the end of Q2:
>>
>> Goals:
>>  - fix all the problems that come up from 0.6 ;)
>>  - Stable ABI/API for ktp-common-internals.
>>  - We want to see kdegames and kipi etc. being able to work with KTp.
>>
>> The intention is to have a very short time between 0.6 and 0.7 with 0.7 just
>> being focussed on stability and not many new features. Just like we did in
>> 0.4->0.5
>>
>> Hopefully this can happen in time for 4.11 to include some KTp.
>> The API will only be "stable" for the KDE 4 releases, we have to break for
>> Qt5/frameworks anyway.
>>
>> ============
>>
>> KTp Active when it's ready
>>
>> Will be released as a  0.1, _only_ when it is ready. Probably end of summer
>> 2013 it depends on who steps up to take it on.
>>
>> =============
>>
>> Once I've finished the model refactoring I am going to be giving LightDM my
>> main priority to get this into extragear. Others need to step up to manage
>> the 0.6 release and make sure it happens in time.
>>
>> David
>
> Soft freeze:  NOW
>
> Hard feature freeze: 2nd March
>
> String Freeze: 16th March
>
> Release: 30th March
>
> Release Party: always
>
>
> If a feature is not completely ready stable and merged by the hard
> feature freeze, it will not enter 0.6.
> We decided 0.7 won't be as far away, so it won't be a huuge deal.
>
> David Edmundson
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy at kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy


More information about the KDE-Telepathy mailing list