[Grok-dev] integrating zest.releaser

[Jan-Wijbrand Kolman]

Martijn Faassen wrote:
> Jan-Wijbrand Kolman wrote:
>> For yesterday's grok release I used zest.releaser to do the actual 
>> tagging and uploading of the egg.
>>
>> Zest.releaser effectively does the things described here:
>>
>>    http://grok.zope.org/documentation/how-to/releasing-software
>>
>> Two suggestions:
>>
>> 1) I'd like to integrate zest.releaser into grok's buildout.cfg file (it 
>> will not be a hard dependency in the setup.py!)
> 
> +1. What would you do with grokcore.* packages and grokui and such though?

Probably the same thing: integrate zest.releaser into the respective 
buildout.cfg files.

>> 2) I'd like to move the afformentioned document to grok's "official" 
>> documentation and add a note to it that most of the work is handled by 
>> zest.releaser.
> 
> I think it might be better to say we follow the ZTK here, and put a link 
> in the official documentation that refers to it, along with a 
> description on how zest.releaser helps automate this.
> 
> http://docs.zope.org/zopetoolkit/process/releasing-software.html
> 
> The idea is to reuse policy from the ZTK where that makes sense. If ever 
> the ZTK policy changes Grok has a say in this too anyway, and if we 
> really don't like it we can alway start maintaining our own.

That's even better indeed. We originally put the "release instructions" 
on grok.zope.org, because they had no official home. Now they have as 
part of the ZTK docs.

So we'll add  a short document to Grok's official documentation that 
refers to the "official" release document, makes note of zest.releaser 
and, eventually, when needed, record any steps that are different from 
the official steps.

regards,
jw