Re: Windows Bugs

Kai-Uwe,

> It was mentioned in many most private communication. So it is not solely 
> my own impression that CinePaint had suffered after that windows 
> portability period. 

There's been a relentless stream of backhanded posts and private chatter 
critical of me coming from people who have an allegiance to another 
project. Anyone can see it's propaganda.

I'm sure that I've never had a public or private technical discussion 
about which Windows code had introduced which Linux bugs. The premise is 
nonsense. The CinePaint code base is POSIX, not Windows. The Windows 
code I developed conditionally compiles on Windows. It can't possibly 
effect Linux.

 > My point was, that I did maintenance of the GTK code with much
 > respect to previous contributions, keeping them alive and help
 > in stabilising them.

That may have been a good point, but by saying my Windows development 
had destabilized Linux CinePaint code you were misinforming everyone.

 > Unfortunedly CinePaint had and has no test framework
> in place to tackle things imediately. So there remains many guessing and 
> finding by accident.

Automated testing has its uses, but with a GUI program like CinePaint we 
have to rely heavily on testers.

There's a QA process. You're not in the loop there because it goes 
through me in off-list conversations. I ask everyone to post to the list 
and bug tracker, but I can't make them.

Robin
-- 
Robin Rowe
CinePaint Project Leader
Beverly Hills, California
www.CinePaint.org
www.cinepaint.blogspot.com
www.linkedin.com/in/robinrowe

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/