[Grok-dev] Grok 1.1 important issues

[Steve Schmechel]

I would like to help test this on Windows with Python 2.6, but I want
to be sure that my procedure is correct for what you intend to
determine.

Could you please describe (or point to a document that describes) the
procedure for testing a potential Grok release?  

Are you testing the latest trunk code (checkout and run buildout), or
are you starting with grokproject and Grok version 1.1a2 and then
pulling in newer code?

Are there any specific changes to the buildout.cfg or other
configuration files?

How deep does the testing go?  Do we just run Grok-specific tests or
recurse into all the tests in the underlying packages and libraries?

How many tests are expected to run and "pass"?

I just want to be sure that if I say "the tests pass", we are talking
about the same tests.  (Assumptions are more dangerous if I do not
find a problem, because there will be no need for someone to further
investigate some specific finding.)

Thanks,
Steve

--- On Fri, 2/19/10, Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:

> From: Jan-Wijbrand Kolman <janwijbrand at gmail.com>
> Subject: Re: [Grok-dev] Grok 1.1 important issues
> To: grok-dev at zope.org
> Date: Friday, February 19, 2010, 7:11 AM
> Martijn Faassen <faassen at startifact.com>
> wrote:
> > Some important issues for Grok 1.1 we should verify
> works:
> > 
> > * Uses the ZTK (plus zopeapp), through groktoolkit.
> We'll just freeze a 
> > recent ZTK...
> 
> Grok's buildout.cfg extends the groktoolkit's grok.cfg
> file. This in turn uses a 
> very recent revision of both ztk.cfg and zopeapp.cfg.
> 
> 
> > * Python 2.6 should work
> 
> See below. 
> 
> 
> > * Running on Linux, Mac OS X, Windows
> 
> * buildout and tests pass on linux (ubuntu, using a
> python2.5 interpreter from a 
> ``virtualenv --no-site-packages``).
> 
> * buildout and tests pass on linux (ubuntu, using a
> python2.6 interpreter from a 
> ``virtualenv --no-site-packages``).
> 
> * buildout and tests pass on mac os x (using a python2.5
> interpreter from a 
> ``virtualenv --no-site-packages``).
> 
> * buildout and tests pass on mac os x (using a python2.6
> interpreter from a 
> ``virtualenv --no-site-packages``).
> 
> * buildout and tests pass on mac os x (using
> /usr/bin/python2.6).
> 
> I hope someone else can check on Windows...
> 
> 
> > * Make sure we don't have missing dependencies.
> allow-picked-versions 
> > set to false in buildout.cfg, running buildout with
> empty egg directory 
> > and no download cache.
> 
> Confirmed: allow-picked-versions is set to false indeed. I
> actually saw the 
> effect of that too as I at one moment accidentally removed
> a version from the 
> versions list and then the buildout would report an error.
> 
> 
> > * new grokui
> > 
> > Anything else?
> 
> What would be the correct release order: first release grok
> and then the 
> groktoolkit, or first the groktoolkit (that then would
> still refer to an older 
> grok) and release grok just after that. I guess the
> latter...?
> 
> 
> regards,
> jw
> 
> 
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev
>