[k3b] What happens after 2.0

[Markus]

Hi.
Are there any plans how to proceed after the 2.0 release?

If no, here's my proposal:
- Create a branch (eg /branches/extragear/multimedia/k3b/2.0) that'll receive 
bugfixes only and keep the string freeze and open trunk for feature 
development and string changes (I already have a list of English typos I 
encountered while translating K3b).

- Backport crucial bugfixes to the branch for two or so months (depending how 
much work that is).

- Tell distributors that they can safely use that branch to generate update 
packages (seems like they currently hesitate to put new 2.0 betas in their 
regular update repos and rather ship the alpha that was current when the last 
"release season" was in fall).
I'd volunteer to bug the openSUSE maintainers about it.

- Encourage distributors to submit bugfixes and that they can of course update 
that branch for their entire 18-24 months support cycle just like they do for 
KDE SC releases.

- To minimize the amount of bug reports for "old" K3b versions, I suggest that 
new releases are made late winter and/or late summer to be picked up by 
Fedora, Kubuntu, and Mandriva in their spring and fall releases.
This is not a suggestion for a 6 months release cycle, btw. Releases can 
happen more or less frequently, but missing those mainstream distos' version 
freeze by a few weeks can't in our interest. ;-)

Bye,
Markus