Home Original page

[python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?

martin at v.loewis.de martin at v.loewis.de
Sat Aug 3 17:42:48 CEST 2013 
Quoting Eli Bendersky <eliben at gmail.com>:

> On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings <larry at hastings.org> wrote:
>> On 08/03/2013 02:08 AM, Larry Hastings wrote:
>>
>> Can we, uh, live with that, for alpha 1?
>>
>>
>> Ned pointed out, signal and zipimport worked on the retry.  So it's
>> sporadic, whatever it is.  I think we can live with that.
>>
>
> This is confusing. Why do we need an alpha release in the first place?
> Is it more important to make it on the exact day than to have a more
> functional release? Assuming that 64-bit Windows 7 is the most popular
> (or close to it) Windows out there today, that sounds like an annoying
> flaw.
>
> The above is genuine will to understand the release process rather
> than questioning your reasoning :-)

In case it hasn't been answered: the point of alpha1 really is to make
a release, and run through the release process. It will likely turn
out that the release process fails in some way, and it may take all
the alphas to get the issues resolved - so it is *expected* that the
release is done despite known issues.

FWIW, I don't consider the failure of the zipimport and signal tests
that relevant, even on Windows. It doesn't mean that the release is
completely useless for users (it could even be that the modules actually
work, just the test runner is flawed).

We hope that end users (and in particular library developers) test the
release, to find out what got broken since 3.3. Again, for that, it isn't
critical that all tests pass, since those users are expected to have
different test cases, anyway.

Regards,
Martin
More information about the python-committers mailing list