[Python-Dev] 2.7 Windows installers (Was: death to 2.7; long live 2.7)

Steve Dower Steve.Dower at microsoft.com
Sun Apr 13 22:02:02 CEST 2014


I replied to the other email before I saw this one.

Consider this my self-nomination to take over, pending a quick email to Microsoft's lawyers to make sure it's okay (it should be, but IANAL and they wrote the policy).

My plan would be to rewrite the installer using WiX but retaining compatibility with the existing MSIs. I'd also automate as much as possible to make it very easy for someone else with the certificates to build/verify the release.

Happy to answer any other questions or provide more background about myself if people ask.

Cheers,
Steve

Sent from my Windows Phone
________________________________
From: Martin v. Löwis<mailto:martin at v.loewis.de>
Sent: ‎4/‎13/‎2014 14:29
To: Benjamin Peterson<mailto:benjamin at python.org>; python-dev at python.org<mailto:python-dev at python.org>
Subject: Re: [Python-Dev] 2.7 Windows installers (Was: death to 2.7; long live 2.7)

Am 10.04.14 03:22, schrieb Benjamin Peterson:
> We'll keep doing what we're currently doing for another year, making
> normal bug fix releases with installers. After that, we _won't_ close
> 2.7 to normal bug fixes as is currently implied by the release schedule.

After thinking about this plan, I believe it is best if I step down as
the Windows installers engineer right away. To my knowledge, no specific
date for the next 2.7 bugfix release has been set, so this should allow
to find a replacement before the next release.

I would have volunteered to do two more releases if these had been the
definite last ones, as it would have been impractical to replace me for
just two releases. If this is going until 2020, anybody up to the task
should start working on it now.

I'll be willing to help anybody taking over with advise, but I'll
consider the 2.7 branch otherwise dead (i.e. not worthwhile
contributing to).

I'll be happy to continue making installers for the 3.x branches,
but if anybody considering to volunteer would do so on the condition
that he/she gets it "all", I'd be happy to hand these other branches
over as well.

Of course, anybody taking over that role would be free to either keep
or replace the current technology (e.g. switching to InstallShield
or WiX or whatever).

The one option I'd rather not support is an "open" committee of
Windows installer engineers. Anybody taking this role will have a
copy of the PSF code signing key, so I'd like to keep this list
rather small, and the people attached to the task.

Regards,
Martin

_______________________________________________
Python-Dev mailing list
Python-Dev at python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/steve.dower%40microsoft.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140413/cf5d73df/attachment.html>


More information about the Python-Dev mailing list