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

List:       kde-devel
Subject:    Getting started (developing KDE)
From:       Chris Arrowood <chris.arrowood () cybertivity ! com>
Date:       2002-12-08 1:59:07
[Download RAW message or body]


I want to start getting familiar with the KDE code and processes in hopes to 
becoming a productive contributer one day.  I have a few questions.  I 
apologize if these are elementary, but I did not see answers for these 
questions on developer.kde.org (although I could have overlooked some...)

With small applications I usually:
- checkout HEAD 
- confirm that it compiles
- make my changes
- confirm that it compiles
- test my changes
- merge any files that have been updated
- confirm that it compiles
- check in

Does that process work for something of the magnitude of KDE?

Should I expect HEAD to compile (esp early in the cycle)?  If not, I cannot 
know for sure that I didn't do something also that broke the build...

Are there any unittests (i.e. cppunit tests) in KDE?  Any mandate for/against 
them?

Thank you for your answers,

Chris Arrowood

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]