2008/11/18 "Martin v. Löwis" <[EMAIL PROTECTED]>:
> While I'm happy that Barry has automated his part to a high degree,
> my part is, unfortunately, much less automated. I could personally
> automate the build process a bit more, but part of it is also testing
> of the installers, which is manual.
Martin v. Löwis wrote:
> While I'm happy that Barry has automated his part to a high degree,
> my part is, unfortunately, much less automated. I could personally
> automate the build process a bit more, but part of it is also testing
> of the installers, which is manual.
Maybe you could dele
Michael Foord writes:
> Installer tests can definitely be automated, and there is also a Python
> API to the virtualbox VM. I wonder if it would be possible to automate
> testing all the installers in various scenarios - each running
> simultaneously in a VM.
Now that would be an impressiv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 18, 2008, at 9:52 AM, Christian Heimes wrote:
Barry Warsaw wrote:
Actually, I've wanted to do timed releases, though I think monthly
is unrealistic. Maybe every two months is about the right time
frame. Timed releases are nice because e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 18, 2008, at 12:46 PM, Georg Brandl wrote:
Barry Warsaw schrieb:
On Nov 18, 2008, at 8:07 AM, Christian Heimes wrote:
Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin suggests, and I agree, that we should release P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 18, 2008, at 5:17 PM, Martin v. Löwis wrote:
From my point of view bi-monthly release are too much. For a ?.?.1
release two months are fine because several issues are found by 3rd
party authors. But after that a release every quarter is suffi
> Martin, maybe we can help you with the installers testing.
Thanks for the offer. See my other message, though - this is not the
point. If everything goes well, offloading testing just means that
I have to wait some time for the testers to come back, and do other
stuff meanwhile.
For the majorit
> Installer tests can definitely be automated, and there is also a Python
> API to the virtualbox VM. I wonder if it would be possible to automate
> testing all the installers in various scenarios - each running
> simultaneously in a VM.
I do use VMs, yes. However, they don't run on my workstation
> Martin, I'm keen on figuring out a way to reduce your workload, and also
> to coordinate releases better between us. I /think/ with timed releases
> I can tag a little early and give you something to work on so that the
> actual release is a matter of fiddling web pages and sending an
> announce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 19, 2008, at 2:18 PM, Martin v. Löwis wrote:
Martin, I'm keen on figuring out a way to reduce your workload, and
also
to coordinate releases better between us. I /think/ with timed
releases
I can tag a little early and give you something
> In which case why not just hold the release until all installers are
> available?
That is how Anthony Baxter handled things, indeed, and I would
appreciate if we would return to that procedure.
> Or are the complainers Python developers who know what goes on behind
> the scenes?
No - typicall
> I will also try to get up early to do the release before my work day
> starts, to better coordinate with Euro time. So expect me on
> #python-dev tomorrow (my morning).
>
> Will that work for you?
If you delay the announcement until the binaries are ready, you should
feel free to work on it wh
Barry Warsaw wrote:
-BEGIN PGP SIGNED MESSAGE-
Let's try this for 3.0rc4 then.
The current release is rc2. Skipping rc3 would confuse people'-)
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pyt
13 matches
Mail list logo
