On Fri, May 3, 2013 at 1:41 PM, Michael Jansen <i...@michael-jansen.biz> wrote: > On Friday, May 03, 2013 02:39:31 PM Aaron J. Seigo wrote: > >> hopefully you can put it in a repository that can be used by kdelibs which > would both get around the 4.x kdelibs freeze *and* prepare it for frameworks. > > Just for clarification because i think i misunderstand something. The proposed > Workflow is > > - Mark some repositories as feature frozen > - Recommend forking them (gitorious, github, gko) for feature development > - Maintain/release patches against kdelibs > > I somehow fail to grasp how recommending having n forks of those repositories > (one for each patch/feature) around makes work for packagers and developers > easier. Or even migration to frameworks/qt5. >
That's not quite what's being said. KDE libs is being split up for Frameworks, some new features have branched out of KDE libs already into their new repos early, and have KDE4 releases. See KActivities or Nepomuk2. KWallet/KSecrets could do the same. David _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
