I have never run meetings, but I ran a free software project for a while, and settled on an arbitrary time-boxed testing and release schedule for reasons that sound a lot like yours, and it seemed to work well, perhaps for reasons that seem a lot like some yours. E.g., "everyone knows the system by which a lot of information moves around" so that they can make routine plans without having to negotiate commitments about what's going to happen in the future.