On Nov 25, 2014, at 2:28 PM, mike thompson <mithomps@redhat.com> wrote:


On 25 Nov 2014, at 10:37, Heiko Braun <ike.braun@googlemail.com> wrote:

I think two weeks is too short if include some upfront clarification/review of the iteration goals and some time QE at the end. IMO 8 weeks is more reasonable.

I guess I was making more of a distinction that we are dev mode right now. Start of a new project(s). Nothing has been QE’d. Right now, we are releasing about about every 4 weeks (but no real schedule).
If you have something to commit in that 2 week window then it will become part of the release. If not, add it to another 2 week window. 

QE will have their own schedule for testing certain features and it will probably not be within the 2 week window. But these are development releases so that is fine.

The product should be buildable and useable every release. Even if some piece is not working in the release, the consumer (of the project) can just keep using the previous release as a new release will happen in another 2 weeks. This way we early feedback with some of the newer features and make changes to them while they are still fresh.

— Mike

This seems reasonable to me, especially since the goal is to facilitate easier integration for consumers.