RE: [Zope] RE: ANNOUNCE Zope 2.2.3 release...
> How long before we end up with 2.2.4 a3 and 2.2.4 b1 with no-one really > knowing what's going on? > Taking what is effectively another point onto the version number doesn't > really help. I can only think of 2.1.7 that was withdrawn, and as long > as 2.2.4 comes along pretty swiftly, there shouldn't really be a > problem, should there? Well, some people perceive it to be problem (and I can't really blame them). What we _really_ need is some regression testing infrastructure. We have started taking some baby steps in that direction with the inclusion of PyUnit, but it will take some time and resources to get a meaningful amount of tests. Hopefully the recent Good Things happening here at DC will mean that the necessary resources will become available to make that happen. In the meantime, since Brian is a poor regression test rig, I plan to have a (generally very short - like a week) beta period for third-dot releases. One beta should usually do it, and it will allow at least for more coverage than I can easily contrive from my desktop as a sanity check. When the test infrastructure is more mature we could revisit this though. Brian Lloyd[EMAIL PROTECTED] Software Engineer 540.371.6909 Digital Creations http://www.digicool.com ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] RE: ANNOUNCE Zope 2.2.3 release...
Brian Lloyd wrote: > > I think that is reasonable - in practice I have found that > many people tend not to upgrade until something is declared > "final", but your point is taken and a little feedback is > better than none. I'll make Monday's release 2.2.4 b1. Please! No! Don't go down the same route as ZPatterns... How long before we end up with 2.2.4 a3 and 2.2.4 b1 with no-one really knowing what's going on? Taking what is effectively another point onto the version number doesn't really help. I can only think of 2.1.7 that was withdrawn, and as long as 2.2.4 comes along pretty swiftly, there shouldn't really be a problem, should there? cheers, Chris ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] RE: ANNOUNCE Zope 2.2.3 release...
On Saturday 18 November 2000 09:07, Joachim Werner wrote: > > FYI - someone has noticed a problem with the posted > > 2.2.3 release that needs looking into, so I've unlisted > > it for the time being. I'll send out a note and re-list > > it after we dig into this a bit... > > Oh no, not this one again ... > > How good that I learned my lesson from the infamous 2.1.x series, when you > always replaced or withdrew the latest bugfix release due to "some errors" > right after we had updated all our servers ... > You mean I'm not the only person who always stays one version behind? (o8 > What about having a "beta" phase for every release, even the x.x.x ones? > I think this would be a great idea... I don't mean to pry, but what level of regression testing do you guys at DC have in place? Or was this a new bug shown up by fixing others? > Cheers, > > Joachim. Have a better one, Curtis Maloney. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
RE: [Zope] RE: ANNOUNCE Zope 2.2.3 release...
> Oh no, not this one again ... > > How good that I learned my lesson from the infamous 2.1.x > series, when you always replaced or withdrew the latest > bugfix release due to "some errors" right after we had > updated all our servers ... I think "always" is a bit strong... > > What about having a "beta" phase for every release, even > the x.x.x ones? I think that is reasonable - in practice I have found that many people tend not to upgrade until something is declared "final", but your point is taken and a little feedback is better than none. I'll make Monday's release 2.2.4 b1. Brian Lloyd[EMAIL PROTECTED] Software Engineer 540.371.6909 Digital Creations http://www.digicool.com ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] RE: ANNOUNCE Zope 2.2.3 release...
> FYI - someone has noticed a problem with the posted > 2.2.3 release that needs looking into, so I've unlisted > it for the time being. I'll send out a note and re-list > it after we dig into this a bit... Oh no, not this one again ... How good that I learned my lesson from the infamous 2.1.x series, when you always replaced or withdrew the latest bugfix release due to "some errors" right after we had updated all our servers ... What about having a "beta" phase for every release, even the x.x.x ones? Cheers, Joachim. ___ Zope maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )