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

List:       kmail-devel
Subject:    Re: Preannounce: Kroupware Project started
From:       Don Sanders <sanders () kde ! org>
Date:       2002-09-11 7:55:15
[Download RAW message or body]

On Wednesday 11 September 2002 11:30, Zack Rusin wrote:
> On Tuesday 10 September 2002 14:49, Matthias Kalle Dalheimer wrote:
> > The project deadline forbids us to follow the normal KDE
> > development schedule, and we are also concerned about introducing
> > instability into KMail and KOrganizer at this point in the KDE
> > 3.1 release cycle. We will therefore create our own branch called
> > kroupware_branch in the modules kdelibs, kdebase, kdenetwork and
> > kdepim. We aim to retrofit the changes on this branch as timely
> > as possible back into the HEAD branch; this will happen in close
> > collaboration with the maintainers of the affected projects, and
> > following the KDE release cycle.
>
> First of all - fantastic news, congratulations and hopefully we can
> help you guys somehow.
> Now if you don't mind a question:
> - what kind of changes to KMail are we talking about here? I'm not
> sure if you know but KMail has been branched lately to undergo some
> very much needed architectural changes. Now it seems that another
> branch is under way. This will make it almost impossible to merge
> all those branches. After only a few days I already had some
> problems merging changes from HEAD to make_it_cool, I can't imagine
> doing that between three branches. I hope we can come up with some
> reasonable solution. I'd propose using your branch for the
> architectural changes which were going to make_it_cool, because I
> can imagine you guys will have to rework/refactor a lot things in
> the process of working on your project in the first place. What do
> you guys think?

Merging three branches would be more work. I'm not sure it would work 
to try to merge his branch and make_it_cool, but I'm 100% willing to 
try if he wants.

Otherwise I'd rather wait until Kalle has finished his work and merge 
it in to make_it_cool (or whatever it becomes) in one big go once his 
work is ready for release.

I'm going to answer a few Qt bugs now and after that I'll port 
KMMainWin to being a kpart, I think this is the kind of thing he'll 
need to do, I'll do this by monday morning, I'll post a patch once 
I'm finished to the list and I hope that he is willing to consider 
accepting my patch into his branch if it's the kind of thing he 
wants.

Basically if there's any duplication of effort between Kalle's plans 
and mine then I'm willing to give those efforts higher priority to 
get them done *now* and submitted to both make_it_cool and Kalle's 
branch but he has to be willing to look at my changes and consider 
integrating them.

Both my girlfriend and my best friend Sam are away now so I have 
*heaps* of free time, especially in the weekends.

But I better answer those Qt bugs now.

Don.

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]