[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta-devel
Subject:    [quanta-devel] Total freeze, KDE 4
From:       Andras Mantia <amantia () kde ! org>
Date:       2005-02-19 10:22:12
Message-ID: 200502191222.16865.amantia () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,

  I was (badly) surprised when I looked at the release schedule and saw 
that we have only 3 days until the total freeze. I will try to make the 
external file parsing to ghather the class information and fix the 
reproduceable bugs, especially the crash/hang/high CPU usage bugs. 
There are not so many (6 reports), and I cannot really reproduce most 
of them. Right now Quanta has 31 open bug:
- 8 crash bugs: 5 related to editing, but as I don't have example files 
I cannot reproduce them, 1 is related to WebDAV, which I couldn't test 
here.
- 6 VPL bugs
- 4 ftp/fish related issues
- 5 again editing related bugs: high cpu/memory usage.
- the rest is various, some are Qt related (maybe I should close them, 
as I cannot fix Qt bugs), others are KMDI related (slow redrawing when 
switching tabs, because the user toolbar is removed and displayed 
again)

So if you can, fix the bugs. Pick the most annoying ones if you don't 
have enough time. ;-)
So prepare for the freeze. After it, you can commit only show-stopper 
fixes and only after a review on the mailing lists.

Secondly, there is a discussion ongoing about KDE's feature on 
kde-core-devel. It has started some time ago, and I'd suggest to follow 
it and add your comments if you have some ideas about what should 
happen there. Shortly, the discussion is about:
- the KDE4 release schedule: now it seems that there will be a KDE 3.5 
*application* only release. This means the same kdelibs is used for 
3.4, but if somebody wants to introduce new features that will work on 
KDE 3.4 base, they can. I don't want to make a kdewebdev 3.5 release, 
to be honest as we have plenty to do between 3.4 and 4.0. I'd rather 
focus on having a more or less stabilized kdelibs 4 and start to port 
Quanta to kdelibs/qt 4 as soon as possible.
But this is my personal opinion only.
- the build system that will be used instead of autoconf/automake: no 
consensus reached yet
- the conversion of the CVS repository to subversion. A test conversion 
was already done, you can experiment with it, but the commits there 
will be lost when the final conversion is done (after 3.4 release is 
tagged). This is there to see how it works and to try to identify 
possible problems. 
- there are other issues that were not so discussed yet. See the "Future 
of KDE Development" thread started by Coolo on 2005-02-14 for details. 
It's a long thread, but interesting for anybody who cares about the 
future of KDE. Related threads are:
"Subversion problems" : started by Coolo on 2005-02-17
"Announcing test svn import": started by Coolo on 2005-02-18


Andras
-- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org

[Attachment #5 (application/pgp-signature)]

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel


[prev in list] [next in list] [prev in thread] [next in thread]