Krita 1.6: my proposal

[Casper Boemann]

Why don't we continue working on 1.6 while the rest of the koffice developers 
start working on 2.0.

Krita should then be disabled from 2.0 until after we release 1.6, at which 
point we copy all of krita from the 1.6 branch to trunk and start doing the 
porting.

The point is that we wouldn't have to stay away from doing core stuff.

We don't even have to decide on a date for releasing 1.6. If in three months 
time we find that kde4 is not so far away we can even decide to skip 1.6 
alltogether

I have seen Boudewijn's list of things we want from kde4 but they don't seem 
very important to me in contrast to the great stride we could be making with 
painterly stuff, scripting and other interesting things. Do we really want to 
suspend krita development for half a year.

On Monday 06 February 2006 19:50, Boudewijn Rempt wrote:
> Okay, this is my proposal for the post 1.5 period.
>
> Two tracks:
>
> * Krita 2.0 -- porting to Qt4 starts as soon as it's possible to run an
> application, say, konqueror, on kdelibs4 without crashing.
>
> * Krita 1.6 -- to be released in September.
>   - This is a feature release.
>   - Core hacking will be limited to adding stuff to existing classes,
> removing and changing existing API's is a no-no, adding new classes, ditto.
> People adding stuff to the 1.6 API _must_ _absolutely_ also add the same to
> 2.0, at the same time.
>   - Someone else must be release dude for 1.6
>   - It may include such plugins from the krita/plugins project as are
> deemed stable by Cyrille.
>
> * Krita-plugins -- if Cyrille agrees, a public release every two months,
>   - without translations etc. Translations will come when stable plugins
> are added to Krita.
>
> I have to say that I envision myself working mainly in Krita 2.0.

-- 
best regards / venlig hilsen
Casper Boemann