> I think it would be sufficient if we will soon announce the renewal of the
> state of soft-freeze. 28. February seems good date.

Sounds good to me. Actually it is the same day I proposed in the etherpad a couple of hours ago :-)
I would still prefer to have a branch for it, but it is not strictly necessary as long as we all agree to avoid potentially "dangerous" commits.
After declaring the soft-freeze we should: 
1) refrain from any kde->tde rename
2) refrain from renaming/moving files around, unless strictly needed. Specifically I would like to avoid new FTBFS such as those that were recently created when docs and icons were updated
3) refrain from adding new apps/enhancement to the trunk
4) create a realistic list of bugs that have to be fixed for R14.0.0 (we can build upon the existing etherpad), review it together and soft-freeze the list as well. Only critical issues could then be added to such list.  

>Note: For final R14.0.0 we should solve NetworkManager8 support, which
>could represent a piece of code that should be pushed, even if the soft-freeze.
It's ok, just put that in the list.

Cheers
  Michele