[Grok-dev] Re: Futuring proofing a pre-grok1.0 project

Martijn Faassen faassen at startifact.com
Mon Feb 25 09:09:12 EST 2008

Lennart Regebro wrote:
> On Thu, Feb 21, 2008 at 3:46 PM, David Bain <david.bain at alteroo.com> wrote:
>> I want to ensure that I'm building an application that can easily jump
>>  to grok 1.0 when it is released.
>>  Basically I'm looking for suggestions on how best to ensure that a
>>  project built with pre grok1.0 (at the moment that would be grok 0.11
>>  I believe) will be easy to port to grok 1.0.
> Well, I don't expect any backwards compatibility changes at this
> point, just more features? Martijn probably has more insight?

There aren't many backwards compatibility issues expected indeed.

The main thing that might break your code is that we'll upgrade to a 
newer version of the various Zope 3 packages depend on. Rather late in 
the process for Zope 3.4, some code was moved around various packages. 
This means that *if* you have imports to zope 3 code, you might get an 
ImportError or hopefully, a Deprecation Warning. Fixing those imports 
should not be a big deal in a typical application.

Of course some internals of Grok do sometimes change, and if you rely on 
them in some way there could be problems. We'd be happy to accomodate 
any issues though, and we'll make sure we'll be releasing a beta and/or 
release candidate.

In short, I don't expect much to worry about - Zope 3 is a stable enough 
base over all. Grok changes a bit more quickly, but most changes are 
internal or just by the addition of new features. We do have quite a 
battery of tests to make sure things still work.



More information about the Grok-dev mailing list