On Wednesday 07 November 2007 11:34:05 Sebastian Kügler wrote: > On Wednesday 07 November 2007 09:51:50 Tom Albers wrote: > > It's news to me too. > > > > I don't think this should be done this way. kdesupport follows kdelibs > > release path. > > > > So they should not use trunk kdesupport to work on the next version. In > > case they want to work on the next version, maybe they should move to > > extragear/libs like any other application/library. > > We need to document that then (adding qca2 to the techbase build > instructions then). If we switch to a released qca in this state, it'd also > need some testing.
Wasn't the original reason for kdesupport to put code there that was required for building KDE? In light of that concept the stable version should stay in kdesupport. I doubt Tom wanted to remove it from kdesupport. If people want to have a place to work on it, they are free to have a working copy in extragear or somesuch to do so, but that is a separate issue from having a realease-ready copy in kdesupport. -- Thomas Zander
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
