Regarding the development cycle and Sept 1 code freeze- in trying to make some contributions myself, I'm left with the feeling that the pace is currently a little too fast. Rather than making Sept. 1 a code freeze, would it be possible to make it a feature freeze? i.e. define a list of features where some of the code may not yet be RTBC on Sept 1, but which must/will be included in the next release? I think Dries had a top 10 list in a previous thread that would be a starting pont for this. -Peter