<br><br><div class="gmail_quote">On Wed, Oct 24, 2012 at 11:43 AM, Thierry Florac <span dir="ltr"><<a href="mailto:tflorac@ulthar.net" target="_blank">tflorac@ulthar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<br>
Le Wed, 24 Oct 2012 07:45:50 +0530,<br>
Milind Khadilkar <<a href="mailto:zedobject@gmail.com">zedobject@gmail.com</a>> a écrit:<br>
<div><div class="h5"><br>
> Hello all Zope Users!<br>
> We are trying to decide on a Zope platform for, say, the next five<br>
> years. We have developed small products on Zope2 and Zope3 between<br>
> 2000 and 2008, and in Grok over the past couple of years, off and on.<br>
> We are looking to build as per customer requirements, and it would be<br>
> common sense to choose the platform as per requirement. However, with<br>
> a small team size, we can't spread ourselves thin over the three<br>
> platforms...Pyramid, Django and GAE also keep beckoning....<br>
><br>
> We have seven revivable products in Zope2 (2.6 - 2.10), including one<br>
> in Plone. Some of them do not open in Zope 2.11...<br>
> Some of them use DTML for no reason now discernable.<br>
> Some of them use a very old version of ZODB.<br>
><br>
> We have one big product in Zope 3.3. Can we attempt converting it<br>
> from Zope 3 to Zope2?<br>
><br>
> We have no real work done in Grok, but there is a level of<br>
> familiarity with it. Newer members of the team know neither Zope2 nor<br>
> Zope3.<br>
><br>
> Making use of our past work is an important criterion for us.<br>
> Training new team members is another...<br>
><br>
> What other things must we keep in mind when deciding on the platform?<br>
> Any pointers would help.<br>
><br>
> Sorry for this rambling question.<br>
> Thanks in advance for your answers.<br>
<br>
</div></div>Using Zope 2 for several years, I switched to Zope 3.3 probably five<br>
years ago and our latest developments since two years are based on ZTK<br>
and ZopeApp. We are really very happy with these!<br>
<br>
Having small teams of developers, mainly coming from the Java world,<br>
training them for recent environments was more "natural" and easier to<br>
them than it was for Zope 2.<br>
<br>
The main problem with these releases is that BlueBream "as is" is a<br>
dead project; I only used it as a base to create my new development<br>
environments based on recent releases of ZTK and ZopeApp packages.<br>
These ZTK and ZopeApp packages are still maintained (last release was<br>
in May, 2012) but don't seems to evolve much actually (even if<br>
development work seems to be visible in Launchpad). Development<br>
community on these packages don't seems to be very active or is, at<br>
least, hard to find! Same for Grok, for which the last release was 18<br>
months ago.<br>
<br>
Excluding Django, Pyramid seems to be the most active project actually<br>
among those you mentioned. And it can include many "old" Zope concepts<br>
(ZODB, traversing...). But I didn't had any time to test it until now...<br>
<br>
Best regards,<br>
Thierry<br>
</blockquote></div>Thanks, Thierry.<br>Actually, there is a recent Grok release that is a well-kept secret: <a href="http://grok.zope.org/releaseinfo/1.5.4/versions.cfg" target="_blank">http://grok.zope.org/releaseinfo/1.5.4/versions.cfg</a><br>
I got the above info when we got into some windows-based problem on Grok and I communicated on the list.<br><br>Besides, the Grok developers feel, probably rightly so, that Grok is more-or-less feature complete and that widely-spaced releases are to be expected. Another explanation is (as quoted): "Another reason why Grok releases do not happen too often these times is,<br>
that Grok meanwhile is merely an umbrella package for a couple of<br>outsourced packages (these grokcore.xxx packages). These packages are<br>frequently updated but normally only as bugfix releases which leaves the<br>Grok version number as-is."<br>
<br>Thanks, again.<br>Regards<br>Milind Khadilkar<br>