-----BEGIN PGP SIGNED MESSAGE-----
Philipp von Weitershausen wrote:
> Tres Seaver wrote:
>>>> Point me at an existing source release, and I'll be happy to generate
>>>> corresponding windows eggs.
>>>> I made windows eggs for the latest version of zope.interface that's in
>>> Great. So we have zope.interface and zope.proxy and there'll be no need
>>> for zope.thread. Which leaves us with:
>> Are you asking that Windows folks run using these alphas as binaries? I
>> don't quite see the benefit.
> So I guess you don't see the benefit of releasing Windows binaries for
> alpha and beta releases.
>>> I realize that those aren't final releases, but they (most probably)
>>> haven't changed significantly after these releases were made, which
>>> would make it a waste of time if I had to tag and tarball them just for
>>> the sake of a different version ID.
>> Doing proper release management can't reeally be called a waste of time
>> (that would include documenting exactly what *has* changed).
> Right. *Proper* release management. I believe we have a volunteer
> release manager for that and for Zope 3.4 it's not me.
Right: you are asking that somebody do the release manager's job, or at
least part of it. I was trying to point out that doing only a partial
job (making binary installers for alphas) is likely to be troublesome.
Note that under our proposed release regime, depending on an alpha makes
*you* and alpha, too; is that what you want?
>> Again, what kind of Windows user are you expecteing (wanting) to test these
> People who want to try out Zope 3.4 on Windows, in particular those who
> want to try out Grok, the buildout instance recipes and Zope-on-Paste on
> We've done some Zope 3.4 alpha and beta released, why shouldn't we make
> Windows eggs for those so that people can actually *try* them before a
> final release?
Until somebody makes a "release manager" call that a package is stable
enough for beta, I'd be really reluctant to ask people to test using
binaries: they won't be able to develop or apply patches to test fixes,
for instance, to bugs in the C extensions.
Making it easier (via documentatin, likely) for *anybody* with an
appropriate toolchain to build Zope's eggs on Windows would help, both
by removing the need to built them before a real release, and by getting
better feedback on platform-specific problems earlier in the cycle.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope3-dev mailing list