> I have nothing against establishing a new branch.
> But I'm not sure that now is the right time.
> 
> We want to establish a new branch in order to integrate new applications? We 
> want to establish a new branch in order to "do new things"? On both I say 
> unambiguous: not now. We need to devote all effort to pushing R14.0.0 out the 
> door. We are too few of us to split our efforts. If we now begin to address 
> new applications or new things, it will have a negative consequence on time 
> to release R14.0.0.

I understood the branch suggestion to mean a way to separate aggressive hacking from R14.0.0 hacking.

> I suggest at this point to completely stop the debate on new applications and 
> pursue exclusively the tasks necessary for R14.0.0. Let them be filled bug 
> reports for new applications and we will pursue them after the release 
> R14.0.0. Keep in mind that our team is small, and that for us was a great 
> luxury to divide our efforts at this time.

Sure, that is good. If we keep using the main trunk as the place to push R14.0.0 related patches, then we should all agree not to push anything esoteric or new. Bug fixes and nominal feature tweaks only. At one time we were at feature freeze but that got lost soon thereafter. Perhaps we should again declare a feature freeze, which then would satisfy Michele's suggestion. But if we go into feature freeze then all of us should focus on R14.0.0 and nothing else. If we again declare feature freeze then that becomes R14-alpha.

-- 

Darrell