New Bugzilla Roadmap

[Frédéric Buclin]

> trunk opens before we freeze for 2.24.  There's several BIG things very
> close on the horizon, and 4 weeks is too short.  Maybe June or July-ish
> would be a good thing, but sticking with the previously scheduled March
> 15th seems like a bad idea at this point.
> 

Instead of debating now when to freeze, we should first unfreeze and do 
some work. In other words: there are many new great things which should 
land this spring/summer, and I think it worths "delaying" our next 
release a bit if we are very close to have some new features fully 
implemented but a few weeks are missing. I think we should discuss this 
point in June, where we could decide what is close enough to get in for 
2.24 (or 3.0), and what is late enough to be delayed till our next release.

I also want to say that from a QA point of view, releasing often is a 
pain too, because having 20 or 200 checkins since our last release won't 
change the number of tests (and consequently the amount of time) 
required to test the new release. So I would tend to say that at some 
point the freezing period is incompressible, even if we would release 
every month (just to say something irrealistic).

So 4 months of development followed by 2 months where the development is 
frozen is a pretty bad ratio IMO.

LpSolit