[Koha-devel] 2.2 branch strategic question

[Paul POULAIN]

Hi,

2.2.4 should be here soon, & i'm wondering what to do with releases.
Let me explain my questions...

I've released a new minor version every quarter. Each contains :
- some bugfixes
- some new features. Those new features didn't change the DB for 2.2.1, 
2.2.2 and 2.2.3, and will change a little the DB for 2.2.4.

With the 3.0 version announced for 2006Q1 (end of...), i'm not sure it 
would be the best solution to continue releasing 2.2.x with new features.
Here is a list of pro and cons i've found.
Feel free to add some of them.

pro :
- new features are always nice to have before next major release
- some of them are very important and could be considered as bugfixes 
(like leader support in 2.2.4, for example)

cons :
- installing a new version every quarter is too much work
- learning what is in a new version every quarter is too much work, 
libraries are missing new features !
- it's too much work to synch 2.2 and head with new feature. That won't 
be easier with new head work !
- new features means ... new bugs !

so, I suggest, after your reactions, feel free to say if we need a poll 
in koha & koha-fr mailing lists or decide.
but i really have no preferred opinion. Maybe a little feeling that we 
could just release bugfixes in 2.2 branch. But not sure.

Note that some features were requested by some customers and requires to 
be quickly written in order to deploy Koha, so i think I was right -from 
my point of view- until now !
-- 
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIGB libre http://www.koha-fr.org)