I planned this to do a bit earlier, but was side tracked. So sorry for the delay and for the announcement on short notice: KDE 3.5 is no longer developed in /trunk, but in /branches/KDE/3.5, KDE 4 development will start soon in /trunk (and move out of work/kde4)

For translations, nothing changed as /trunk/l10n is generated from KDE 3.5 as planned.

If you want to continue with KDE 3.5 development, then you use once svn switch $PROT://svn.kde.org/home/kde/branches/KDE/3.5/$MODULE instead of svn update in $MODULE (no need to recheckout). After writing this mail I will switch some trunk modules to use Qt4, so don't be suprised if your trunk checkout will break heavily. This will be a tough time as we transition between KDE 3 and KDE 4 and I hope that tools like kdesvn-build will help you through it.

Please note though, that while KDE 3.5 is our next release, it's no longer the main target: KDE 4 aka /trunk is. So when you want to continue with KDE 3.5 development, make sure to also put your changes in /trunk.

Much of it is still open, but the current release schedule is the current consensus of the KDE core developers and I put it online under:
http://developer.kde.org/development-versions/kde-3.5-release-plan.html

Please note that next Monday (yes, in 3 days) the feature list closes, so if you still have pending ideas you better commit them soon. As KDE4 will take some more time and KDE 3.5 is definitely the latest feature release of the KDE3 series, everyone in the team will have to be a bit more flexible, but still we should try to follow the rules that assured the high quality of past releases.

A specialty in the KDE 3.5 release schedule is that the feature freeze is _before_ this year's akademy and the message freeze is _after_ it to avoid forseeable frustration from translators as I'm just too sure developers won't be able to stick to a message freeze during akademy (my hopes for a kept feature freeze are a bit higher though - as I will be around :):)