I think targetting KDE-3.4 should be fine. By then KDE-3.4 should be
pretty well deployed and it also reduces the "comptibility confusion"
of KDevelop. (KDE-3.4 - KDevelop-3.4)<br>
<br>
Of course, if someone wants to "backport" incompatible changes to
remain compatible with KDE-3.2 I think we should accept those patches.<br>
<br>
// jens<br><br><div><span class="gmail_quote">On 10/21/05, <b class="gmail_sendername">Amilcar do Carmo Lucas</b> <<a href="mailto:amilcar@ida.ing.tu-bs.de">amilcar@ida.ing.tu-bs.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br><br>Matt can you move the work/kdevelop3.4 branch to kdevelop/3.4 ?<br>Next time you move a branch please contact me first because otherwise the<br>website breaks.<br>Thanks.<br><br>Now a question for all KDevelop 
3.4 developers:<br>Which API should we use for KDevelop 3.4 ?<br>KDE 3.2<br>KDE 3.4<br>or<br>KDE 3.5 ?<br><br>IMHO we should use KDE 3.4 API, because then we would remain compatible with a<br>large number of user that do not want/can update to KDE 
3.5<br><br><br>Regards,<br>--<br>Amilcar Lucas<br>Current webmaster<br>The KDevelop project<br><br>_______________________________________________<br>KDevelop-devel mailing list<br><a href="mailto:KDevelop-devel@barney.cs.uni-potsdam.de">
KDevelop-devel@barney.cs.uni-potsdam.de</a><br><a href="http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel">http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br></blockquote></div><br>