Re: Modularization and other languages' bindings (was: The Future of our Frameworks)

2011-06-10 Thread Arne Babenhauserheide
On Monday 06 June 2011 21:05:41 Luca Beltrame wrote: > In data Monday 06 June 2011 19:26:38, Sebastian Kügler ha scritto: > > (I took the liberty of adding kde-bindings to the CC of tihs specific topic) > > > We want to make it possible to use our frameworks in Qt projects without > > significant a

Re: No more release schedules.

2011-06-10 Thread Scott Kitterman
On Thursday, June 09, 2011 06:08:56 PM Tom Albers wrote: > > Having KDE's own packages also released in an uncoordinated > > fashion > > Wow. Who suggested that? That would make a mess indeed. I certainly did not > ever suggest that. If you think so, pleas reread all my mails. I've > suggested th

Re: No more release schedules.

2011-06-10 Thread Jos Poortvliet
On Friday 10 June 2011 01:00:45 Andreas K. Huettel wrote: > > I just read a very good novel where all such talk about "Software > > Collection" > > > or "Platform" was aptly called "commercial bulshytt". I think many of us, > > including your "only-users", would appreciate it if you all there > >

Re: Use of uninitialized value in qt-copy/bin/syncqt line 337.

2011-06-10 Thread Oswald Buddenhagen
On Wed, Jun 08, 2011 at 03:26:00PM -0700, Nick Savoiu wrote: > Use of uninitialized value in utime at > /scr/tahoe-s1/nos/prjs/kdesrc-build-1.13/dwnld/qt-copy/bin/syncqt line 337. > this is fixed in a newer qt version. the warning as such should be harmless. >> Visit http://mail.kde.org/mailman

Re: KDE at the Qt Contributors Summit

2011-06-10 Thread Frederik Gladhorn
Hi, this is for attendants of the Qt Contributors Summit. Make sure that all the info from the KDE wiki pages is also on the dev net wiki! In other words: take your session proposal and put it into the schedule. All topics should be listed here: http://developer.qt.nokia.com/groups/qt_contribu

Re: No more release schedules.

2011-06-10 Thread Thiago Macieira
On Friday, 10 de June de 2011 10:56:11 Andreas K. Huettel wrote: > Exactly. Having a larger number of small tarballs can be just fine if done > properly. But, they should still have the same release schedule, version > number, and should be tested to work together. I.e. released as a working > w

Re: No more release schedules.

2011-06-10 Thread Andreas K. Huettel
> > So forget about monolithic tarballs please. It is clouding the issue. > Exactly. Having a larger number of small tarballs can be just fine if done properly. But, they should still have the same release schedule, version number, and should be tested to work together. I.e. released as a wor

Re: No more release schedules.

2011-06-10 Thread Eric Hameleers
On Fri, 10 Jun 2011, Modestas Vainius wrote: > On penktadienis 10 Bir?elis 2011 00:09:16 Eric Hameleers wrote: > What do small tarballs have to do with this disintegration? I do understand > that you dislike small well-split tarballs but, seriously, don't blame > everything on them. It's only a di

Re: No more release schedules.

2011-06-10 Thread Modestas Vainius
Hello, On penktadienis 10 Birželis 2011 11:49:47 Eric Hameleers wrote: > Again, monolithic tarballs or not, this is not the topic. Coordinating > the release process for all the individual submodules is what is going > to make or break KDE's acceptance. Do I have to remind you of the > consequenc