Preannounce: Kroupware Project started
zack at kde.org
Wed Sep 11 02:30:01 BST 2002
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
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?
A great many people think they are thinking when they are merely
rearranging their prejudices. -- William James
More information about the kde-core-devel