+1 This makes more sense than putting a sudden unannounced stop to new features. Possibly Weldon means "on a case by case basis after risk assessment". However, announced stability periods at the end of milestones is a good practice. For example, since we have been focussing on development for a while, and there are many open JIRA bugs, we could consider rounding off the year with a "no new features and only bugfixing" period for 3-4 weeks starting December 1, to round off the year. We can fork and create a development branch to support some new work during this period. Going forward, we can try to plan for milestones and repeat this plan-development-stabilization process.
Thanks, Rana On 11/7/06, Tim Ellison <[EMAIL PROTECTED]> wrote:
I wouldn't go so far as to label issues as "won't fix" unless they are really high risk and low value items. It's useful to go through a stabilization period where the focus is on getting the code solid again and delaying significant new functionality until it is achieved. A plan that aims to deliver stable milestones on regular periods is, in my experience, a good way to focus the development effort. Regards, Tim
