No bugfixes from final beta?!
Hi Brian,
From ZWN: The "no changes between last beta and final" approach is one that we are going to adopt from now on. Even seemingly dead-simple bug fixes can turn into (different) bugs, and being very strict about allowing any changes between a final beta and a release will produce fewer surprises. I need to update the official release policy to reflect this.
Sorry, but this seems kindof silly... what's the point of doing a final beta if you're not going to make any changes (even fixing bugs!) after it? Surely you might as well just release it as the final then? cheers, Chris
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Chris Withers Sent: Wednesday, April 18, 2001 5:27 PM To: Brian Lloyd Cc: zope@zope.org Subject: [Zope] No bugfixes from final beta?!
Sorry, but this seems kindof silly... what's the point of doing a final beta if you're not going to make any changes (even fixing bugs!) after it?
Surely you might as well just release it as the final then?
I suspect this means that if there are bug reports they will instead release a beta 2 (or beta next) and wait a week until there are no problems reported. Then when the final is released (having already been tested without changes) and the non-beta users upgrade to it, they're less likely to run into problems due to "fixes" that did not go through beta testing. Am I on base here? _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
Chris Withers wrote:
Sorry, but this seems kindof silly... what's the point of doing a final beta if you're not going to make any changes (even fixing bugs!) after it?
Surely you might as well just release it as the final then?
cheers,
The way I understand it is that if more important bugs are found in a beta, then another beta is issued. After a suitable period has passed without substancial bugs reported, the final beta becomes the release version. This is so that *any* fixes are checked in beta first, not just released on assumption that nothing was broke. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
The way I understand it is that if more important bugs are found in a beta, then another beta is issued. After a suitable period has passed without substancial bugs reported, the final beta becomes the release version. This is so that *any* fixes are checked in beta first, not just released on assumption that nothing was broke.
This is at least how it SHOULD be handled ;-) And of course it makes sense to not introduce new features in the beta phase, because those might cause new bugs. Joachim
Joachim Werner wrote:
The way I understand it is that if more important bugs are found in a beta, then another beta is issued. After a suitable period has passed without substancial bugs reported, the final beta becomes the release version. This is so that *any* fixes are checked in beta first, not just released on assumption that nothing was broke.
This is at least how it SHOULD be handled ;-)
And of course it makes sense to not introduce new features in the beta phase, because those might cause new bugs.
Joachim
Yes, in theory, new features should only be added in alpha, but I'm not sure this has been abided by strictly for Zope releases, although I could be wrong. If it hasn't been abided by in the past, it will need to be now to make this scheme workable IMHO. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
participants (4)
-
Casey Duncan -
Chris Withers -
Joachim Werner -
Ron Bickers