Greg Smith wrote:
> So why not do that? Developing new features is fun and tends to attract
> sponsorship dollars. Testing a frozen release, finding bugs, and
> resolving them is boring, and no one sponsors it. Therefore, if you let
> both things go on at once, I guarantee you almost all of the community
> attention will be diverted toward new development during any period
> where both are happening at the same time. Give developers a choice
> between shiny and profitable vs. dull and unpaid, and they'll focus on
> the former every time. That means that there's no possible way you can
> keep new development open without hurting the dreary work around
> stabilizing the beta in the process. You have to put all the fun toys
> away in order to keep focus on the painful parts.
"put all the fun toys away in order to keep focus on the painful parts"
--- pure poetry.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
