[Zope 2] Skipping beta releases?
Hi, the current release model of Zope 2 is based on doing at least one beta release for minor releases (Zope 2.7.X where X > 0). I have the strong impression that beta releases are not adopted and tested by most people. They usually use the "final" version of a release. So most bugs are discovered in final releases and not in beta releases. People interested in the most current version can and do download the sources from the CVS or SVN. So I propose to skip beta releases for minor releases in the future. Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people. Any comments? Andreas
On Sun, 03 Jul 2005 09:13:48 +0200, Andreas Jung <lists@andreas-jung.com> wrote:
Hi,
the current release model of Zope 2 is based on doing at least one beta release for minor releases (Zope 2.7.X where X > 0). I have the strong impression that beta releases are not adopted and tested by most people. They usually use the "final" version of a release. So most bugs are discovered in final releases and not in beta releases. People interested in the most current version can and do download the sources from the CVS or SVN. So I propose to skip beta releases for minor releases in the future. Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people.
Any comments?
Andreas
Hi, you are right in my case, I almost never test beta releases of minor releases. Regards, Florian Schulze
On Sun, 2005-07-03 at 09:13 +0200, Andreas Jung wrote:
Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people.
Any comments?
+1 ... alphas/betas should be done at your discretion.
On 3 Jul 2005, at 15:16, Chris McDonough wrote:
On Sun, 2005-07-03 at 09:13 +0200, Andreas Jung wrote:
Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people.
Any comments?
+1 It's a sad state of affairs that the wailing and gnashing of teeth only ever happens after a third-dot final release and few people bother with the betas. In the light of the effort needed to produce a Zope beta I support the decision. I personally would still continue doing betas for things like CMF, but then again the work needed to put together a release is a lot less. And I still live under the illusion that those betas see a modicum of testing ;) jens
--On 3. Juli 2005 15:32:29 +0100 Jens Vagelpohl <jens@dataflake.org> wrote:
I personally would still continue doing betas for things like CMF, but then again the work needed to put together a release is a lot less. And I still live under the illusion that those betas see a modicum of testing ;)
Creating the release archive is not really the problem. The big pain in the a** is the software package product on zope.org and dealing with it :-/ Andreas
On 3 Jul 2005, at 15:48, Andreas Jung wrote:
--On 3. Juli 2005 15:32:29 +0100 Jens Vagelpohl <jens@dataflake.org> wrote:
I personally would still continue doing betas for things like CMF, but then again the work needed to put together a release is a lot less. And I still live under the illusion that those betas see a modicum of testing ;)
Creating the release archive is not really the problem. The big pain in the a** is the software package product on zope.org and dealing with it :-/
I suspect the biggest problem there is the appservers and the underlying portal software as a whole, not necessarily the piece that you touch when making releases. Even with a better "Software Product" product you would most likely still see slow reaction times when uploading files or creating the documentation items (including their automatic cataloging) inside a relase. I fight the same problems when doing a CMF release. jens
On 7/3/05, Andreas Jung <lists@andreas-jung.com> wrote:
the current release model of Zope 2 is based on doing at least one beta release for minor releases (Zope 2.7.X where X > 0). I have the strong impression that beta releases are not adopted and tested by most people. They usually use the "final" version of a release. So most bugs are discovered in final releases and not in beta releases. People interested in the most current version can and do download the sources from the CVS or SVN. So I propose to skip beta releases for minor releases in the future. Alpha and beta releases are fine for major releases. Beta releases for a minor release can be made if there are some changes or fixes that must be tested by people.
Any comments?
For pure bugfix releases, unless the bugfixes are expected to have side-effects, then a beta is not needed, you are right. Skipping betas may mean that you need to make more non-beta releases, but then.... that's still less work. :-D -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/
participants (5)
-
Andreas Jung -
Chris McDonough -
Florian Schulze -
Jens Vagelpohl -
Lennart Regebro