Gideon under KDE2

Ralf Nolden nolden at kde.org
Thu Nov 15 18:31:02 UTC 2001


On Wednesday 14 November 2001 06:13, you wrote:

Ok, I just stumbled over this while looking over my emails. I'm at the 
TrollTech booth running a small KDE subset with promoting KDevelop for KDE/Qt 
development here but unfortunately TT doesn't have an internet connection. I 
barely could persuade someone to let me plug my laptop on his line for 
sending mails once a day in the morning. So sorry for the delays; there may 
be even more up until next week because tomorrow I'll leave Las Vegas to 
visit my cousins in Oregon for holidays. They do have a phone line and an 
internet connection but I have to see the circumstances first before 
promising I get a connection working at all ... In case I'll fail totally, 
I'll ask Keith Packard who lives in Portland also to let me use his network 
once a week or so to keep up.

Now, regarding this whole issue, I've made some thoughts also. We have a 
couple of issues here that I would like to address. What we should do is put 
out KDevelop 2.0.3 or something as KDevelop 2.1 out. At least that symbolizes 
that we support KDE 3 fully; even though we didn't raise the major version 
number.  KDevelop 3 should be kept named gideon on the binary so people can 
use whatever they want intermediately. Releasing a KDevelop version with KDE 
3 that works is *very* crucial. We need to

- make current developers pick up Qt3 and KDE3 by porting
- attract new developers to develop for KDE3 

and that should be done right away and as soon as possible so all the apps 
that are currently available for KDE 2.x should be available as fixed, 
updated versions  within a couple of weeks.  I would like someone to exchange 
the admin.tar.gz tarball of kde-common/admin to HEAD as soon as the 
KDE_2_2_BRANCH is tagged for the KDE 2.2.2 release including kdevelop 2.0.2. 
I've fixed those issues that appear with compatibility in the templates but 
the version checks in the admin.tar.gz need to be updated if 2.0.2 is to be 
released also with KDE 3 beta1. So please someone volunteer to do that and 
monitor that as I am absolutely not able under the current circumstances to 
keep track of this; my connection times and schedule are far from having a 
reasonalble environment to work in.

When it comes to Gideon, we'll release that also with KDE 3 as a developer 
version. The architecture is clear and done, Roland told me in Oakland he 
already ported QextMDI to HEAD and use it inside gideon; so if that is 
completed we should release it so that we 

- attract other volunteers to help us make it perfect during the KDE 3 
release cycle and finish it up to a good extend by KDE 3.1 or 3.2,

- make the API and plugin architecture available to the broad public to write 
plugins.

Regarding my own work, I will need to put the crosscompilation into KDevelop 
2.0.2 first I guess; this seems to be very urgent as Sharp is bringing out a 
new PDA running QPE and embedded Linux. 

Roland and Falk can schedule things for KDevelop 2.0.2 with Waldo and Dirk 
for the respecitve tagging and releaseing. Please make sure that the version 
for KDE 3 contains an updated admin directory in the tarball and an updated 
admin.tar.gz in the templates directory.

Ralf
> To me the case is clear, KDevelop-2.0.2 with KDE-3. The version number
> indicates that this is a minor bugfix release. I
>
> f we wanted to indicate that we adapted to KDE-3 and Qt-3, maybe we
> should raise it to 2.1.0 instead.
>
> Also, gideon stays in cvs until ready.
>
> Ralf, what do you say?
>
> Roland
>
> --- "F at lk Brettschneider" <gigafalk at yahoo.com> wrote:
> > Harald Fernengel wrote:
> > > does ist make sense to release KDevelop 2 along with KDE3?
> > > People will expect
> > > new features with a new major release, which we don't have.
> >
> > The people will want KDevelop also for KDE3.
> > Technically, we need to recompile and relink to KDE3/Qt3.
> > Otherwise, people would need kdelibs2 additionally installed to run
> > KDevelop.
> > It would be the same situation as with KDE2 and KDevelop-1.3;
> > KDevelop-1.4 was just thought as 1:1 port to the new KDE generation.
> >
> > > Maybe we should
> > > detach KDevelop 2 from the KDE release cycle and release one or two
> >
> > minor
> >
> > > bug-fix releases when the time is right.
> >
> > I love to be in the KDE release cycle. The short time distances
> > between
> > their releases enables to keep KDevelop very synchronized with the
> > latest bugfixes without any effort for us.
> > For example: today I fixed an evil memory leak but unfortunately I
> > must
> > wait until KDevelop-2.0.3 that fortunately could be soon, the
> > KDE3-beta1
> > date.
> >
> > > For KDE3 I suggest a parallel Gideon Beta 1 or RC 1 release.
> >
> > In my opinion the user of KDevelop is the target group for a release
> > with KDE, not possible developers of KDevelop. There are daily cvs
> > snapshots for the latter.
> >
> > New version means to make users more happy not to show that there's
> > still something going on. ;-)
> >
> > Don't get me wrong, in the long run KDevelop-3 will be the next
> > generation but it's not today. Distributors would be confused, users
> > would be disappointed with the downgrade. Detach Gideon from KDE
> > release
> > cycles, stabilize version 2 WITHOUT ADDING NEW FEATURES.
> >
> > Ciao,
> > F at lk
> >
> > > Harry
> > >
> > > > Hi,
> > > >
> > > > Roland Krause wrote:
> > > > > I'd suggest to try and keep it KDE-2 compatible as long as
> >
> > possible. At
> >
> > > > > least until the first beta release of KDE-3. Actually we will
> >
> > not
> >
> > > > > release anything with KDE-3, or?
> > > >
> > > > Until there's nothing comparable we'll release KDevelop-2.0.x
> >
> > with KDE-3
> >
> > > > because it's already now ready to use, stable and the same
> >
> > full-featured
> >
> > > > as with KDE-2.
> > > > Anyone with a different opinion?
> > > >
> > > > Ciao,F at lk
> > > >
> > > > _________________________________________________________
> > > > Do You Yahoo!?
> > > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > >
> > > >
> > > > -
> > > > to unsubscribe from this list send an email to
> > > > kdevelop-devel-request at kdevelop.org with the following body:
> >
> > unsubscribe
> >
> > > > »your-email-address«
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-devel-request at kdevelop.org with the following body:
> > unsubscribe »your-email-address«
>
> __________________________________________________
> Do You Yahoo!?
> Find the one for you at Yahoo! Personals
> http://personals.yahoo.com
>
> -
> to unsubscribe from this list send an email to
> kdevelop-devel-request at kdevelop.org with the following body: unsubscribe
> »your-email-address«

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list