The case for a kdelibs 4.8

[Kevin Krammer]

On Thursday, 2011-09-29, Rolf Eike Beer wrote:

> The reason to stop master was (as far as I understand) to make the
> frameworks branch easily to maintain. If someone is working on 4.8
> (bugfixing, features) all this has to be ported to frameworks, too. So you
> develop a moving target on a moving target.

What about a more stricter than usual policy for additions to 4.8?
Like every new feature wanted in 4.8 has to go through reviewboard for 4.8 and 
frameworks 5.

That way the developer doing the feature work for 4.8 will also take care of 
the forward porting task.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110930/81b7dcdb/attachment.sig>