On Thu, 2003-10-23 at 06:31, Michael Scherer wrote: > On Thursday 23 October 2003 11:10, Quel Qun wrote: > > On Wed, 2003-10-22 at 20:57, Han Boetes wrote: > > > David Kobler wrote: > > > > Can't we just set a simple standard to TEST YOUR PACKAGES before > > > > uploading > > > <...> > > > Simple test cases, a minimal test plan and a few release procedures > > could be automated and should not be so much of a burden once they > > are established. It's called investment, and I thought that was what > > a commercial company had to do. > > so, you propose to launch konqueror before uploading and having some > automated script to see if it work ? have you sometime to test kde ? > Something automated, yes. E.g. when one installs KDE, konqueror should at least be able to use Mdk bugzilla.
> > Note: These are just 2� thoughts. I am only sad to see that nothing > > changes despite years and years of disappointment. > > well, i do not see anything to do, so, yes, this is always the same > problem, but, we have no easy solution. This is QA field of competence: help define specifications, elaborate tests plans and define procedures to ensure (a minimum of) compliance to the product definition. There are professional people who know how to do that. Minor test items could easily be delegated to the cooker crowd, but packages should have to pass a minimum set of (semi-)automatic tests before being released. Mdk obviously tries to take a bite in the corporate market pie, but I have been using cooker for years and years, and it is very difficult to develop and maintain kde apps. To start with, kdevelop (in my opinion the best linux IDE) is never functional. KDE/QT is a huge beast, but the problem came most of the time from packaging and/or lack of reactivity. Yes, vi or emacs are usable, but I definitely think kdevelop, along with glade and co., should be protected as gems if mdk wants to attract more developers. Good ideas shouldn't depend on editor skills. If the maintainer does not use it, he should delegate or maybe just give up and put it in contrib. Once again, I am just trying to be analytic here, please ignore all the residual subjective accents. -- Quel Qun <[EMAIL PROTECTED]>
