KDE/4.11 branched what to do with kde-workspace?

[Sebastian Kügler]

Hey,

On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> So the kde-workspace dudes decided they don't want a 4.12 release and that
> they'll do a LTS 4.11, fine, how do we fix that branch wise?

After carefully reading everybody's opinion, I would like to make kde-
workspace master our KF5/Qt5 branch, for the following reasons:

- It will likely be impossible to merge frameworks into master later
- We do not have anybody willing to maintain kde-workspace[master]
- kde-workspace master and plasma-frameworks master would then be both on 
  KF5/Qt5
- merging master into KF5 is not a 10 second job, it wasn't a walk in the park 
  last time I did it (granted, that's hopefully alleviated with the freeze)
- It won't be possible to build k-w[master] against 4.x, so it's not a "silent 
  unexpected behavior"
- The whole team feeling responsible for this code has decided to move on, 
  what more do we need, really?

In my opinion it's wrong to try to optimize our development process for people 
who use git-based builds. We do releases for that (and using git won't have a 
lot of benefits in terms of new features or lots of fixes, since we release 
regularly, and nothing will pile up this way.

I'm committed to working on this code a lot, so I'm one of the stakeholders.

Also, the messy kdelibs branch naming strategy doesn't scale. We'll run into 
this exact same discussion again and again as we start porting over more 
modules. Plasma is just early here, but not an exception in any way.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9