Guys,
I agree with Neil ... it's not the length of the development part of the
cycle, it's the length of the beta testing.
I do think an online bug tracker (bugzilla or whatever) would help. I also
think that having a person in charge of testing would help as well ... no
biggie, just
On Tue, Nov 18, 2003 at 09:42:31AM -0800, Josh Berkus wrote:
(Oddly enough, my problem in doing more testing myself is external to
PostgreSQL; most of our apps are PHP apps and you can't compile PHP against
two different versions of PostgreSQL on the same server. Maybe with User
Mode
Josh Berkus wrote:
Guys,
I agree with Neil ... it's not the length of the development part of the
cycle, it's the length of the beta testing.
I do think an online bug tracker (bugzilla or whatever) would help. I also
think that having a person in charge of testing would help as well ... no
On Tue, 18 Nov 2003, Andrew Dunstan wrote:
Josh Berkus wrote:
Guys,
I agree with Neil ... it's not the length of the development part of the
cycle, it's the length of the beta testing.
I do think an online bug tracker (bugzilla or whatever) would help. I also
think that having a
HOWEVER, a release cycle of *less than 6 months* would kill the advocacy vols
if we wanted the same level of publicity.
I do support the idea of dev releases. For example, if there was a dev
release of PG+ARC as soon as Jan is done with it, I have one client would
would be willing to test it
On Wed, 19 Nov 2003, Christopher Kings-Lynne wrote:
HOWEVER, a release cycle of *less than 6 months* would kill the advocacy vols
if we wanted the same level of publicity.
I do support the idea of dev releases. For example, if there was a dev
release of PG+ARC as soon as Jan is done