[Grok-dev] Re: AW: Re: Grok 0.11 released!

Martijn Faassen faassen at startifact.com
Sun Nov 11 01:46:55 EST 2007

Tres Seaver wrote:
> The first point is that whoever put the '.dev-r###' eggs out on a public
> server made an error:  if you don't have the time to do proper release
> management, then don't release at all.  We've spent more effort on the
> argument now than it would have taken to do the releases.
> That said, if merging a feature branch requires picking up unreleased
> packages, then the merge should not be done, period:  merging in that
> state is like merging with failing unit tests.

It's silly to call released packages unreleased. These packages are 
released, otherwise we couldn't have used them in the first place. In 
july, the state of the art of buildout that we knew of was to pick up 
the newest packages ever, even if they were completely ugly.

I don't think the release procedure of these packages was proper, and 
they're ugly, but so were most of the Zope 3 package releases until 
quite recently. Don't think that because something is called 3.4.0b2 
it's actually any more cleanly released than 3.4.0a1.dev-r78838, because 
really it wasn't. Only in the last month or two did Zope 3 packages 
start to get released more or less properly, and Grok has been using 
eggs since july.

We've been eating dogfood for a while now, and since we started eating 
it first, we have gotten the runs earlier too. It doesn't really help to 
keep pointing at our behind as we know we need to clean it up. :)



More information about the Grok-dev mailing list