[Kroupware] Re: Preannounce: Kroupware Project started

[Zack Rusin]

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.

=46irst of all - fantastic news, congratulations and hopefully we can help=
=20
you guys somehow.
Now if you don't mind a question:
=2D what kind of changes to KMail are we talking about here? I'm not sure=20
if you know but KMail has been branched lately to undergo some very=20
much needed architectural changes. Now it seems that another branch is=20
under way. This will make it almost impossible to merge all those=20
branches. After only a few days I already had some problems merging=20
changes from HEAD to make_it_cool, I can't imagine doing that between=20
three branches. I hope we can come up with some reasonable solution.=20
I'd propose using your branch for the architectural changes which were=20
going to make_it_cool, because I can imagine you guys will have to=20
rework/refactor a lot things in the process of working on your project=20
in the first place. What do you guys think?

Zack

=2D-=20
A great many people think they are thinking when they are merely
rearranging their prejudices. -- William James