On Friday, 2013-03-29, dE . wrote: > See, we all agree with the fact that KDE SC is a complicated project and > it's a good design; for starters Akonadi is the only piece of software > proving the likes of MS exchange. But the project doesn't have enough > developers to satisfy the release needs, especially if it's @ 6 months. Well, I concede that it is hard to see from an outside perspective and that attempts to clarify misconceptions are only helping tiny bits at a time, but I'll try again nevertheless :) The main point is, I think, that there is no such thing as a KDE SC project. Traditionally it was nice to have all products of KDE contributors from different problem domains as a set of source packages (and consequently as a set of binary packages) at somewhat predictable times. It has some nice implications like getting attention of user, distributors and reporters likewise, more than any of the single products, especially the smaller or more specialized ones, would get. The drawback is that this also generates some misconception regarding the development process, e.g. making it hard or impossible for outsiders to see that each product has its own development speed and is often developed in much longer cycles than the SC release would suggest. For example different product teams have different strategies on how they use git branches, how and when to allow new dependencies, etc. It could very well be that "release together" effort will be discontinued in favor or smaller collections or something entirely different. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
Attachment:
signature.asc
Description: This is a digitally signed message part.
___________________________________________________ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
