[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu-devel
Subject:    Re: [Kde-edu-devel] Is it time to branch the module?
From:       Haavard Froeiland <havard () student ! unsw ! edu ! au>
Date:       2001-10-24 23:13:03
[Download RAW message or body]

Ups, didn't read this list before I send a reply to the other e-mail list. 
This sounds fine with me. But I agree with Waldo that it would be hard to 
maintain two branches. And for me I'm only using KDE3 cvs and it's therefor 
hard to check if things work back in 2.2 branch.

Greetings Haavard

On Thursday 25 October 2001 06:10, Andy Fawcett wrote:
> Hi folks,
>
> With yet another application (KGeo) joining the project, it has become
> apparent that our cvs module is going to get really complicated soon
> because of the difference between Qt2 and Qt3.
>
> At the moment, most users are still on KDE2.x/Qt2.x, but a lot of
> developers are producing apps for both old and new systems. In just one
> area, the use of .ui files, this is already causing a problem or two.
>
> So, several people have suggested that it is time to branch the module,
> and have HEAD for Qt3/KDE3 code and KDE_2_2_BRANCH for Qt2.x/KDE2.x
> code. This would mean that developers would *probably* have to maintain
> two versions of their code, but it should make life a whole lot easier.
>
> Doing this would also bring the module into line with virtually the
> rest of KDE cvs.
>
> Comments? Complaints? Objections?


_______________________________________________
kde-edu-devel mailing list
kde-edu-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-edu-devel

[prev in list] [next in list] [prev in thread] [next in thread]