Yeah yeah, thanks thanks! Now both of you get back to work :D
Just kidding, thank you all! We rock!
Now let's start talking about the 0.4 :D
A couple of ideas for the release cycle:
1) Let's keep track of the new features so that it will be easier to
write the release announcement... I already started a pad here [1],
please take the time to add a line when you push some new feature or
when you fix some important bug. Also don't forget to blog!
2) common-internals is now a library, but it's not api/abi stable so
let's break it, clean and refactor stuff and try to make it look as much
as possible like a real library before 0.4, and try to have at least a
part of it "stable" for 0.5! Anyway since we have several modules using
it, if we want to have an 0.4 release, I suggest we have a
common-internals mini-freeze a few weeks before the freeze for the other
repos. No api break allowed during that freeze, but new methods and
classes are allowed. What do you think?
Cheers,
Daniele
[1]http://kde-telepathy.notes.kde.org/4
On 24/01/12 23:06, David Edmundson wrote:
....and an absolutely massive thanks to Martin. Without him, and the
much needed tidying up he did after 0.2, none of this would be
possible.
I use KDE Telepathy every day, and have scarcely had any issues at all
with using it as my primary client in the past 6 months. We rock.
Thanks again to everybody.
Dave
_______________________________________________
KDE-Telepathy mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-telepathy
_______________________________________________
KDE-Telepathy mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-telepathy
