|
On Friday 29 August 2008, Matthew Woehlke wrote: > Allen Winter wrote: > > On Friday 29 August 2008 14:56:02 Matthew Woehlke wrote: > >> Tom Albers wrote: > >>> The release team is considering making two tags which contain the > >>> stuff (kdesupport parts) you need for KDE stable and trunk. Can we wait > >>> for that to happen before discussing this even more? The idea is that > >>> you can check out that tag and have all the right versions. > >> > >> ...and will simply building the latest trunk/kdesupport still work, I > >> hope? > > > > The whole point will be to stop using trunk/kdesupport. That's where > > the development takes place. We should be building only against > > stable external packages. > > Meh, but then I have to worry about *upgrading* them ;-). Right now I > just build the latest rev. of the whole enchilada. (And it's a LOT more > convenient to have one kdesupport than phonon+plasma+strigi+automoc+...) Well although they call it a tag it is quite possible to bump code in these tags. When a new phonon is required for trunk, for example, they could simply unlink the trunk-stable/phonon and copy the new stable phonon over it. It doesn't have to be static for all time. > Besides, for those willing to do it, I'd think it's better to have more > people banging on head before release cycles kick in, no? I think this is so we can get closer to "summer in trunk" myself. By focusing more testing attention on kdesupport we necessarily subtract from the trunk we *should* be focusing on, /trunk/KDE. ;) Besides which, those who are willing to do it can still build trunk/kdesupport like always. The new tag would be for those who are tired of having random kdesupport modules break their whole build. :) Regards, - Michael Pyne |
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<