We should agree on the standard procedure for the nightly/trunk of Spark. I am used to a situation, were the trunk is moving with developer tested patches that are commited. This allows the testers to “bake” the patch and if it is buggy the developer has to rework the patch.
Since we have a situation in project were test teams/capacity is not closely connected to the developer (most of us are not sitting in one building), I would argue in favor of a relaxed patch mode for the trunk. A branch may be cut, if we thing 2.6.0 is final and we want to go for a RC2.
Walter