Kevin Grittner wrote: > Greg Smith wrote: > > > 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. > > Frankly, part of the problem is that it's hard for many of us to see > how to contribute effectively for most of these five months or so, in > general. In particular, if someone *is* willing to pay you to work > on developing a feature during these months, but not to work on any > other PostgreSQL development, what do you recommend?
Yea, that is a problem. Years ago the commit process was all driven by a few individuals, and our group has been successful at distributing that workload, so my hope is that the stabilization phase will also lend itself to distributing the workload someday too. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
