Alpha 5 or Beta 1? ( was Re: [Bug 45848] ... )

[Roberto Raggi]

On Monday 12 May 2003 14:08, Jens Dagerbo wrote:
> On Monday 12 May 2003 14.28, Roberto Raggi wrote:
> > hmm, what is pre alpha5!??! i hope the next release will be the first
> > beta, and i hope we will release beta1 before the nove hrady meeting!! so
> > we can try to convince some core kde developer to start use kdevelop 3 :)
> >
> > in fact now with "kdevelop 3" is possible to develop and maintain large
> > projects, like kdelibs and kdebase, but my impression is that many kde
> > developer are switching from emacs/vi to kate :(
> >
> > /me is very impressed from kate in cvs head!
> >
> > anyway, i don't think it is a good idea to release another alpha, maybe
> > it could be better a nightly(or a weekly) release.
>
> At least two things have been discussed that might shake things up a bit:
> 1) Source restructuring
> 2) "make all functions using filenames use KURLs instead" (from the TODO on
> the homepage) - debatable if KURL is the best way, but we need to do
> _something_.
>
> IMHO, both needs to be done before the next public release, and I guess the
> outcome will decide if we're ready for beta or not. 1) shouldn't really
> make much trouble, but 2) affects a lot of code!

sure!! i agree (2) affects a lot of code! but we have 3 months :) 
what we needs is a good schedule.

my personal TODO list for the next three months is:
  1) merge my new class browser in HEAD
  2) remove the lib/sourceinfo
  3) commit my changes to C++ parser, this patch contains
      the AST nodes for expressions. with this patch is possible
      to "finish" the code completion and the realtime syntax checker,
      because using these new nodes, we can write a TreeWalker 
      that computes, in realtime, the type of an expression
  4) improve the automake project

other things that i would like to see finished in kdevelop are:
  1) using KURL (at least) in the lib/interfaces
  2) using KAction in our version control parts
  3) and a better "QextMDI". i know that f at lk
      starts to play with it!! and from what i've seen
      he has some nice idea :) 
  4) removes the "1000" different project managers that we have in cvs! 
      it isn't so simple maintain all this kind of projects manager! maybe,
      we can try to improve the custom project manager.

maybe, (3) and (4) could be scheduled for kdevelop 3.1, because my feeling is, 
their are not so simple to implement, but i don't see any problems with other 
points.

ciao robe