21 messages in org.kde.kde-core-develRe: Plan to transition to KDE Frameworks| From | Sent On | Attachments |
|---|---|---|
| David Faure | Jun 6, 2011 4:43 pm | |
| David Faure | Aug 6, 2011 6:31 am | |
| Eike Hein | Aug 6, 2011 6:56 am | |
| Michael Pyne | Aug 6, 2011 7:09 am | |
| David Faure | Aug 6, 2011 7:52 am | |
| Stephen Kelly | Aug 7, 2011 4:44 am | |
| Michael Jansen | Aug 7, 2011 5:43 am | |
| Allen Winter | Aug 7, 2011 5:58 am | |
| Albert Astals Cid | Aug 7, 2011 6:12 am | |
| Aaron J. Seigo | Aug 7, 2011 6:19 am | |
| Allen Winter | Aug 7, 2011 6:26 am | |
| Stephen Kelly | Aug 7, 2011 6:55 am | |
| David Faure | Aug 7, 2011 7:21 am | |
| Stephen Kelly | Aug 7, 2011 10:06 am | |
| Scott Kitterman | Aug 7, 2011 9:42 pm | |
| Kevin Ottens | Aug 8, 2011 12:27 pm | |
| David Faure | Aug 9, 2011 4:05 pm | |
| Scott Kitterman | Aug 9, 2011 4:25 pm | |
| David Faure | Aug 10, 2011 5:39 am | |
| Scott Kitterman | Aug 10, 2011 8:49 am | |
| David Faure | Aug 11, 2011 2:25 am |
| Subject: | Re: Plan to transition to KDE Frameworks | |
|---|---|---|
| From: | Scott Kitterman (kd...@kitterman.com) | |
| Date: | Aug 9, 2011 4:25:54 pm | |
| List: | org.kde.kde-core-devel | |
On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
On Saturday, August 06, 2011 09:32:02 AM David Faure wrote: ..
The next step is to backport the few bits of new api that went into master and that application developers started using, into the 4.7 branch of kdelibs. I'll work on that, but help is welcome too.
...
This plan seems to be contrary to the KDE Point Release Policy [1]. At this point I don't see an easy way out, but it would be good if a cutoff point for these additional API changes in 4.7 could be set (perhaps no later than 4.7.1's release). [1] http://techbase.kde.org/Policies/Minor_Point_Release_Policy
Under some conditions, the policy allows new API in a stable branch. We decided that these conditions were met :-)
(IIRC there were only three, and they were rather minor and safe; a KUrl::List constructor, a new exported method, a new signal)
Just to be clear then ... No further API changes are planned for incorporation in the 4.7 branch? From a distro perspective it matters to me that the API be stable after our release (which will be with 4.7.1 or 4.7.2 depending on when they are released), so as long as it's those and no others I'm perfectly happy.
Scott K