Fwd: KDE Frameworks Release Cycle

[Kevin Ottens]

On Wednesday 21 May 2014 11:28:45 Aaron J. Seigo wrote:
> On Wednesday, May 21, 2014 10:17:15 Kevin Ottens wrote:
> > The aim is the following in my books:
> Thanks :)
> 
> > Obviously the difficult point as certainty goes is the last one, as it is
> > highly dependent on the amount of contributions which mainly come from
> > volunteers and on the amount of time available from reviewers.
> 
> One needs to free themselves of the idea that just because a branch is ready
> that it must be merged immediately. Let branches queue up if they come too
> fast. An empty queue is no problem, and a full queue merely asks for
> patience. With monthly releases, the wait will never be long and almost
> certainly less than the current 6 month wait time for a regular release.
> 
> Reflecting on the last 10 years of kdelibs development, I do find it hard to
> imagine that a given framework will have more than 5 API additions for any
> number of consecutive months. Frameworks going through that kind of churn
> are usually new and not really ready for strong quality commitments. IOW, I
> doubt it will become an issue in practice.

I agree there. Just wanted to point out the limit of the certainty in that set 
of goals.
 
> > This type of branch got actually
> > discussed before making the initial proposal, it's not that we don't like
> > the idea at all, it's that we don't feel confident to make it work at that
> > point in time.
> 
> Even with a single stable branch owner?

Yes, that's the exact option we thought about, but you need someone willing to 
do the job.

> I completely agree that the "everyone backports" does not work for something
> like Frameworks (for various reasons), and that is not what I was
> suggesting.

Sure.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20140521/0e6a6f1c/attachment.sig>