Release management thoughts for Dapper Drake

[Ruben Vermeersch]

On Sat, Oct 15, 2005 at 04:41:27PM +0100, Jeff Waugh wrote:
> > I might also be okay with your concept if the components I care about are
> > brought to date (because they belong to a goal, or an exception depends on
> > them), but that's not really the way I want to get what I want.
> 
> We have a slightly different goal for this release, so we get to think about
> the problem slightly differently. I am sure we will update much of what we
> ship, but we will do it 100% *knowingly* in each case, instead of just being
> hammered by the general churn.

Does this also mean that there will be no huge breakages etc, in other
words: the dapper working branch will be a much safer place then the
breezy branch. Making sure it doesn't break (too much) right from the
start sounds like a great way to attract more testers.

Is this what's intended?