Moving 3.5 development into branches/KDE/3.5
ben at meyerhome.net
Wed Jun 1 02:36:22 BST 2005
On Tuesday 31 May 2005 8:17 am, Benjamin Reed wrote:
> On 5/31/05, Brad Hards <bradh at frogmouth.net> wrote:
> > 0. Only port kdelibs to Qt4 at this stage
> > 1. Do the application porting as an experiment/testcase only - a few
> > tricky apps from kdebase, a couple of little ones, a couple of bigger
> > ones. Don't try for a complete, stable port.
> > 2. Spend the time between now and the 3.5 freeze on kdelibs polishing -
> > can we get 100% code coverage in tests? could we valgrind kdelibs (tests)
> > completely clean? Could we document it better?
> This would also give us time to work on the new build system; right
> now I'm anxious to start working on KDE4 for Qt/Mac, but the current
> autotools stuff *sucks* for doing Qt/Mac work (for various reasons).
Speaking of which the previous thread on the build system kinda tottered out.
Has anyone else had a chance to play around with all of the different tools
mentioned to provide more feedback on the topic?
Public Key: http://www.icefox.net/public_key.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel