Just a friendly reminder: the cvs HEAD is frozen for features and string changes.

Excluded from string freeze: pure bug fixes in the strings (e.g. errors in the strings that would lead to user errors) Not excluded: systematic style guide or grammar fixes (there was enough time for that).

As usual: if you're in doubt, post your patch on kde-core-devel (or kde-i18n-doc for string changes).

I'd welcome if you could shift your concentration on regressions and bugs that have severity >= major in bugzilla (on your own scale of course). There will always be bugs, so there is little point risking new bugs while fixing not so important bugs :)

Here is the latest groupware patch. I fixed some issues with the free/busy handling, but it's still not good enough and I don't have any more time for coding today :-(

So I took the consequence and disabled all the configuration for now and put disabling guards on all the code. This means it is officially not supported, and the user has no way to get at this functionality. It is possible for developers to do so, though - either reenable the prefs page groupware checkbox or set "Use Groupware Communication=true" in the "Group Scheduling" configgroup in korganizerrc. When this setting is not present or false, there is no change in korganizer functionality. When it is set, the automatic groupware scheduling is working; the freebusy prefs page is shown; and the gantt view is in the event editor.

The idea with this is of course that I can commit the patch and work with incremental changes instead, and that others can start hacking away on the code. That way we can also discuss smaller and more separate issues than try and comment on a ~100KB patch. But still without giving the user the option of accessing it so no confusion will be made.

I'm sure someone will point out that since HEAD is now (or soon) frozen, there is no reason to accept this patch. But I fear that if it's not committed, then the last four days work will be lost, because I will be back to porting the patch to HEAD again when it opens.

And of course, if we do make a separate kdepim release anyway, it would be good to get this in.

I just got a green light on checking in the gw patch, so it's in now :-)

Instructions on trying the stuff out:

Set "Use Groupware Communication=true" in the "Group Scheduling" configgroup in korganizerrc and restart korganizer.

1. Bo tries to get the groupware_branch in. We will sort out smaller issues later.
2. We will delay Exchange support to the release in two or three months. Contrary to groupware_branch, the concept of exchange support never has been really tested apart from Jan-Pascal. We might keep it as KOrganizer resource, though (we shipped it earlier anyways).
3. In order to prepare the independent KDE-PIM release, we should have another meeting asap.