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

List:       kde-release-team
Subject:    Re: KDE Frameworks Release Cycle
From:       Harald Sitter <apachelogger () ubuntu ! com>
Date:       2014-04-29 12:33:12
Message-ID: CAEc+18E5vdjrti5rk=LFLSdKhYV+fz1_W1c8A3-q3bo5cX0GTA () mail ! gmail ! com
[Download RAW message or body]

ahoy, quick question that just when we discussed this in kubuntu:

On Sun, Apr 27, 2014 at 3:15 PM, David Faure <faure@kde.org> wrote:
>  * Everything is developed in master, so each release will contain a few new
> features and bugfixes;

> Of course, going with this type of cycle comes with some price of its own:
>  * Features in released modules can only be introduced in a very fine grained
> way so as to not jeopardize the stability;

I suspect that's bad wording, but those two things sound contradicting to me.

If everything is developed in master (i.e. features are not developed
in a feature branch and then merged into master) but features mustn't
affect the stability, how do you ensure latter if someone develops a
feature locally (alas, no feature branch on git.kde.org) and then
pushes at any day (since there is no feature freeze)?

HS
_______________________________________________
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]