integrating zest.releaser

[Jan-Wijbrand Kolman-3]

Hi,


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!)

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.

Regards,
jw

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Reinout van Rees]

On 2009-10-08, Jan-Wijbrand Kolman <janwijbrand@...> wrote:
>
> 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!)

Full agreement, of course :-)

Reinout

--
Reinout van Rees - reinout@... - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Vincent Fretin]

+1
Vincent


On Thu, Oct 8, 2009 at 10:33 AM, Reinout van Rees <reinout@...> wrote:

> On 2009-10-08, Jan-Wijbrand Kolman <janwijbrand@...> wrote:
>>
>> 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!)
>
> Full agreement, of course :-)
>
> Reinout
>
> --
> Reinout van Rees - reinout@... - http://reinout.vanrees.org
> Software developer at http://www.thehealthagency.com
> "Military engineers build missiles. Civil engineers build targets"
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev@...
> https://mail.zope.org/mailman/listinfo/grok-dev
>

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Martijn Faassen-2]

Jan-Wijbrand Kolman wrote:

> Hi,
>
>
> 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?

> 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.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Jan-Wijbrand Kolman-3]

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

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev

[Martijn Faassen-2]

Jan-Wijbrand Kolman wrote:
> Martijn Faassen wrote:
[snip]

>> 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.

+1

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
https://mail.zope.org/mailman/listinfo/grok-dev