[IMPORTANT] stopping development

George Kiagiadakis kiagiadakis.george at gmail.com
Tue Sep 13 22:16:24 UTC 2011


On Wed, Sep 14, 2011 at 12:52 AM, Michael Drüing <michael at drueing.de> wrote:
> Hi,
>
>> 13.09.2011 20:22, Patrick Spendrin wrote:
>> Hi everybody,
>>
>> I just tried to push a fix to kdelibs master - when that failed, I
>> was told that doing that is restricted to David Faure. Since we can't
>> fix master anymore, we will stop fixing the kdelibs (and other repos
>> that have such restrictions) master branch for windows for now. This
>> means, simple bug fixes will be done only before release (e.g. when
>> the release branch has been made).
>>
>
> This sounds disturbing. Am I right in assuming this is only temporary? E.g. until 4.7 is "stable" and development on master can continue? Is there anything online where I can read about that policy change?
>
> -Michael

http://lists.kde.org/?l=kde-core-devel&m=130740387112872&w=2

In short, master is frozen because we are not going to release kdelibs
4.8 or 4.9 (or any later 4.x version). There will only be bugfix 4.7.x
releases. The rest of the kde-sc 4.x series will continue to be
released, based on kdelibs 4.7. This will continue until kde
frameworks 5 are ready.

I don't see though why this affects the kde-windows project. You can
still continue doing what you were doing before, you just need to
switch to using kdelibs from the 4.7 branch rather than master and
commit fixes to the 4.7 branch (only fixes though, not new features).

Regards,
George


More information about the Kde-windows mailing list