What will happen with the both 1.x and 2.x trees in the future when KDE 2.0 final is released?
jbb
jbb at ihug.co.nz
Thu Dec 30 23:21:40 GMT 1999
Hi,
I have new features in the upcoming kdevelop1.1 release that are not in
kdevelop2.
I've not ported my stuff to kde2 because
a/ it's not a stable system to develop from
b/ it's api is not yet stable
c/ I like to work on one thing at a time
d/ I suspect I'll be reworking a lot of my stuff to take advantage of the new
things in kde2 (almost definately)
e/ other things in kdevelop2 are likely to change
d/ It's not clear how long "only a matter of months before KDE 2.0 " really
is :-)
e/ You can use 1.0 to work on 2.0 stuff.
not withstanding a and b and d, kde2 looks _excellent_, and I hope to be working
in it soon, and yes, it will be a pain to move my stuff over, but not
unmanagable.
PS. I can't speak for the others, of course :-)
--
Regards,
jbb
http://homepages.ihug.co.nz/~jbb
On Fri, 31 Dec 1999, you wrote:
> Hello
>
> It seems to me like the both KDevelop sourcetrees, 1.x and 2.x has different features, some
> things are different, some features are in one of the trees and not in the other. There are now
> only a matter of months before KDE 2.0 is released, and my guess is that most people will
> start to use this 2.0 release instead of 1.x since most dists which include KDE, will use the
> KDE 2.0 version since that's the newest one.
>
> It's possible that I've missunderstood how the development is done. Are the both sourcetrees
> maganed in paralell so that new features are added to both threes at the same time?
> And / or can new features in the 1.x tree easilly be copied into the 2.0 tree?
>
> The reason for this mail is mostly because I'm interested in how you vill solve this, if there
> even is a problem. Have you guys in the developerteam made any plans for how to make
> the features come together?
More information about the KDevelop
mailing list