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. Or is this just the recommendation for this case? Mike _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
