On 04/03/2006, at 4:59 AM, Jim Gallacher wrote:
More in the way of a general observation rather than on these specific issues, but I wouldn't necessarily mark things as resolved just on the basis of the fix being committed. For the big changes at least, I think we should see some testing on a couple of different platforms. Maybe we could announce development milestones and ask the community for a round of testing? Issues would be marked as resolved after each milestone test cycle. That way we are more likely to catch problems early and hopefully reduce the time it takes for the next beta cycle. We should do whatever we can to avoid the 7 months it took to get 3.2 out. (Actually, it was even longer than that, as Grisha first mentioned a 3.2 release last spring). Ideally trunk would always be in a stable enough condition that we could do a release within a month of making a decision.
Okay. Pity there isn't a status that a issue can be parked in meaning "waiting
to be reviewed/tested", or did I just miss it. BTW, shall I still start closing off issues fixed in 3.2.8 and earlier. Graham
