4.5 Release Schedule

Stephen Kelly steveire at gmail.com
Sun Apr 11 22:55:51 CEST 2010

toma wrote:

> Final problem we had this cycle was changing dependencies until late in
> the schedule. So we added a dependency freeze at the hard feature freeze
> time. People should by then know what they want to add as features for
> that cycle and think about the dependencies they need. During the
> dependency freeze it is not allowed to introduce new dependencies or raise
> the version of existing dependencies.

I agree with the existence of a dependency freeze, but not allowing the use 
of newer versions of existing dependencies happens before even a beta 
release. If there are bugs in dependencies fixed in patch-level releases 
distros will ship the new patch level release anyway, right? 

Or does that apply only to major.minor releases, and not patch releases? I 
think patch level versions are generally not checked for in CMakeLists 

All the best,


More information about the release-team mailing list