Depends a bit on how things are set up. In some agile development
methods they just start dropping features to hit a target ship date. So
if there are bugs in some component and time is getting short, that
component may get dropped and prioritized for the next release. Ideally
you're putting out updates or fixes once a month, or even more often, so
dropping something out now won't mean a huge delay before it finally
gets added in but still gives the customer something now rather than later.
CB
Jane Lee wrote:
On 10/12/07, Chris Blouch <[EMAIL PROTECTED]> wrote:
but you have to finally put your foot down and
ship something.
The idea is that you have a code freeze some time before going gold.
During that time no new functionality will be included for that
release, but within the existing code all major bugs need to be fixed.
When the code post-freeze is stable and bug-free-enough, it goes
gold.
cheers,
jane
