[Grok-dev] Final touches for a 1.0 "proper"
sebastian at urbantalk.se
Mon Sep 28 05:13:29 EDT 2009
I believe we still have community documentation that isn't updated.
The least we should do is clearly mark them as
"This document hasn't been verified with Grok 1.0 and may be
Preferably with an explanation on the community docs process and link
to the Grok-doc information.
If we don't do this, it will reflect badly on the great work that has
been done. I would argue that this is a show stopper.
On 27 sep 2009, at 23.01, Jan-Wijbrand Kolman wrote:
> The 1.0b2 has been out for a week or so. At the time of the release we
> thought we could do the final very soon after the beta. I'd still like
> to do that :-)
> A few questions:
> * So far there haven't been any showstoppers for a 1.0, right? If
> are, we should see if we can fix them.
> * It is not really a show stopper, it would be nice if someone
> Uli?) could have a look at what I skethced out here:
> See also the earlier "using zope.testbrowser to test for Unauthorized
> exceptions and updated zope.publisher with IReRaise exception support"
> * Besides the regular release procedure, do we need to take extra
> Where do we want to have the release announcement published? What kind
> of message do we want to present in the release announcement? Who
> to help write one?
> * We could aim for Wednesday 30/09 for the release.
> * Anything I didn't think of?
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev