RE: New release plan

> -----Original Message-----
> From: Tom Huybrechts [mailto:tom.huybrechts@...]
> Sent: Tuesday, March 10, 2009 12:47 PM
> To: dev@...
> Subject: Re: New release plan
>
> I prefer the original idea (a 'voluntary' restraint on
> committing during the quiet period) over branching each time.

I have seen software projects that take this approach. Every single one of them runs into the problem where the software gets completely destabilized from a stampeding herd of checkins after a period of not being able to check in. This is exactly the type of problem that continuous integration is supposed to solve in the first place.

I'm an infrequent committer at best, so if this is how people want to do it, I'll go along, but it will become a problem as more people contribute to the core.

> I'd also like to suggest we take this time to review commits
> others have done. Not every problem (e.g. backward
> compatibility) will be caught by the tests we have now, but
> some extra eyeballs will surely help. Perhaps it would help
> to send a mail (automatically) every time the quiet period
> starts stating changes that have been made since the last
> release ? Or a link to a Fisheye page where can you can see
> them all at a glance.

  +1 on this idea.

  -- Dean

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...