Re: KOffice Split, before or after 2.3 ?

On Wednesday 10 November 2010, Inge Wallin wrote:
> But I still think that removing stuff is perhaps not the most sensitive
> thing  to do.
The main reason for doing it is to avoid confusion, it could lead to the idea 
that there are two places for application development. Lets takes "kspread" as 
an example (but it applies to group B application), if kspread is left in 
trunk/koffice with this name, then it will be unclear where the kspread 
development happen in trunk/koffice/kspread or in the git repo based on 
koffice-essen.

Also, once the board has taken a decision, it is rather possible that the 
koffice repository itself will be removed at (or around) that point.

-- 
Cyrille Berger Skott