Re: [Klibido-devel] kde4

[Stefan <ste...@gm...>]

On Thursday 03 January 2008 14:25:27 Bauno wrote:
> On Thursday 3 January 2008 11:39:23 Stefan wrote:
> > I don't think porting to kde4, refactoring kde3 version and then porting
> > those changes is not a good idea, because refactoring probably changes
> > most of the code which we'll than have to port twice.
>
> Of course, this is the downside...
>
> > Also, the kde4 version
> > needs some refactoring, like model/view programming and I don't really
> > like the idea of 2 refactorings.
>
> Me neither. So you think it'd better if the two versions evolved
> independently for code? Only "ideas" should be ported between the two
> versions? :)
>
> > I also noticed the code is messy, so maybe we can better go for a
> > complete rewrite and only copy back some usefull stuff which doesn't
> > require much changes.
>
> Be aware that rewriting != refactoring, and usually takes much longer.
>
> > Does KJove have a cvs/svn/git/... somewhere so we can look at it?
>
> Nope...and I don't think the code can be made public right now...too
> embarassing.
>
> > What do we do with version control? I don't care if we stick with cvs or
> > move to svn or git, but I'd like to check in my changes as fast as
> > possible if we go for the port.
>
> KLibido is on cvs.sourceforge.net, and I think it should remain there.
> KLibido4 can be placed anywhere: in the same repository as a subdir, or as
> another module, or on SVN or git. Dunno.
> Questions: when will KDE4 be released? When will it be "universally"
> adopted? When do you think we could stop maintaining the kde3 version? Ok,
> I know, in fact I already stopped maintaining it a year ago or so :-\ ;-]

kde4 is tagged tomorrow and released next week. Universally adopted, no idea, 
but not in the next few months I think (pure speculation of course).
You can stop maintaining the kde3 version any time you want of course, but 
maybe the first release of the kde4 version is a good time? When we reach 
this point I think kde 4.0.1 should be out and be more stable and widely 
adopted.

Maybe it is smart to keep the 2 versions in the same repo and if cvs is giving 
us any problems we can always move to somewhere else? There are cvs2git tools 
so this shouldn't be much of a problem.