[Grok-dev] Neanderthal II possible sprint topics

Martijn Faassen faassen at startifact.com
Tue Sep 8 17:13:33 EDT 2009


Reinout van Rees wrote:
> On 2009-09-08, Martijn Faassen <faassen at startifact.com> wrote:
>> * We got to release Grok 1.0. I prefer to get that over with on day 1. A 
>> few people should review the issues and then release.
> The two things that pop into my head as "that needs checking/decisions":
> - zope.something.wsgi had a small bug with not using zope.conf product
>   configuration.  Uli has fixed it, but this needs/needed a new
>   zope.something.wsgi release.  Needs checking whether it happened.
> - The multiple-templates-in-one-dir-gives-unneeded-warnings bug: integrate the
>   branch that's available or not?
>> * Merge new template registration branch into grokcore.view. We cleaned 
>> this up, this needs a final review and a merge.
> Ah, ok.  That's my above point 2 :-)

We need to figure out whether we want to risk this before 1.0 or not. 
I'm a bit wary to release this at 1.0. The CodeView/View changes are big 
enough, I think..

>> * Investigate the use of hurry.resource as an official part of Grok 
>> proper. Also look at integrating z3c.hashedresource by default
> Some colleages are drooling all over their keyboards in sheer delight
> everytime they hear "hurry.resource".  So +1 on that from the it-is-useful
> viewpoint.

Man, I didn't realize it actually made people drool. :)



More information about the Grok-dev mailing list