Preferred way to report problems
Andreas Pakulat
apaku at gmx.de
Tue Nov 7 15:47:04 UTC 2006
On 07.11.06 16:16:27, Christian Schneider wrote:
> I'm new to the list. I currently use KDevelop for hacking on code for my
> diploma thesis, and I will do so for some months. The project itself is
> QMake-based and uses Qt4 for the GUI, the core makes heavy use of C++
> templates, typedefs, nested classes and that kind of stuff. So I think
> it's quite a good testbench for the C++-parser and code completion.
>
> I would like to help improving KDevelop by reporting problems, and I
> encounter a lot of it during my work. How do you like me do that?
First of all: Use KDevelop3.4 directly from subversion, if you're not
doing that already. There won't be any new features/large bugfixes on
KDev3.3...
Then as long as 3.4 is not released yet, I think reporting problems here
is best. If you don't get an answer within a week or so, file a
bugreport to keep track of the problem.
And for interactive question-asking feel free to join us in #kdevelop on
irc.freenode.org.
Andreas
--
You need no longer worry about the future. This time tomorrow you'll be dead.
More information about the KDevelop-devel
mailing list