[Grok-dev] 1.0 status and post-1.0 developments

[Uli Fouquet]

Hi there,

Martijn Faassen wrote:

> I think we have two major projects that we need to dust to settle on 
> before we can go 1.0. I think both projects are involved enough to 
> warrant another 1.0a release as well:
> 
> * during the recent sprint JW and I worked on updating Martian to 
> understand inheritance better. We got quite far but we have still some 
> ways to go in finishing it and updating existing grokcore.* packages to 
> work with it. This will then help us solve the view inheritance problem
> 
> * Uli and Michael are working on improving the paster setup story with 
> grokcore.setup. What's the status on this?

This issue has at least two goals, which both handle with `grokproject`
more than with `grok` itself:

 - generate the configuration files by buildout. This seems to be ready
   for release (it's a `grokproject`-only topic), but we could wait with
   the grokproject-release until the other step is finished.

 - move the startup Python code of former grok projects in a reusable
   'external' module `grokcore.startup`. This was more or less ready for
   release until Michael noticed action on `zope.app.wsgi`, which 
   requires some more discussion from our side.

   We could release a `grokcore.startup` package anyway and then update
   grokproject to make use of it (also releasing a new grokproject).

I might add another topic:

* The new grokui.admin with security update notification should be 
  used in new grokprojects. I can care for this tomorrow.

[snip]

Best regards,

-- 
Uli

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090212/d52c32cb/attachment.bin