From: "Mike A. Harris" <mharris(a)redhat.com>
Considering now that we have announced some dates in the beta
installer screens, and we've indeed not been able to meet one of
the dates, this very much illustrates that Red Hat's previous
policy of not pre-announcing dates of things was very well
thought out and rational, because now that the date has been
missed, we are seeing people rant and rave about it.
Since this is intended to be a community project, I have viewed
these release dates as managerial goals to help the redhat external
participants manage their resources. We have a loose idea of
when the next milestone is so we can prioritize our self imposed
1. install or upgrade to new release
2. start reporting burst of bugs from the errors
found only in first use/install phase
3. watch bugs, track personally important issues, make patches
etc. if we want fixed in next release
4. get some paying work done
5. notice new release is nigh and try to push our personal
agendas some more, e.g., new kernel patch for touchpads or
6. stabilize systems for upgrade, make backups etc.
Having goal dates makes the above much easier, IMHO.