"Martin v. Löwis" writes:
> People will never ever test nightly builds. Been there, done that.
> Instead, the nightly build process will break, and nobody will fix
> it for months (or even complain, for that matter).
Certainly seems to be past experience.
I know Martin knows this, but for other
Am 30.10.2010 14:29, schrieb Dirkjan Ochtman:
> On Sat, Oct 30, 2010 at 14:09, "Martin v. Löwis" wrote:
>> I don't feel like producing a complete list of build steps; the entire
>> process takes about four hours.
>
> So is most of this scripted, or is there just a process in your head?
Define "m
On Sat, Oct 30, 2010 at 14:09, "Martin v. Löwis" wrote:
> I don't feel like producing a complete list of build steps; the entire
> process takes about four hours.
So is most of this scripted, or is there just a process in your head?
> The steps that are difficult to automate are:
> - code signin
> Right, the effort of those people is obviously the limiting factor
> here. Automating builds sounds like a good step forward. What are the
> sticky bits here? Martin, Ronald, how much of the process is not
> automated, and why is automating hard?
I don't feel like producing a complete list of bu
On Sat, Oct 30, 2010 at 05:22, Nick Coghlan wrote:
> Ultimately, the frequency of releases comes down to the burden on the
> release manager and the folks that build the binary installers. Any
> given RM is usually only responsible for one or two branches, but the
> same two people (Martin and Ron
On Sat, Oct 30, 2010 at 7:39 AM, Dirkjan Ochtman wrote:
> That's an average of 4 (if you include .4) or 4.5 months (PEP 6
> specifies 6 months, but some of the parts seem outdated). I think
> releasing each month might be a bit ambitious, but it would be great
> to drive down the release interval
On Fri, Oct 29, 2010 at 21:54, Barry Warsaw wrote:
> Another quick thought. What would people think about regular timed releases
> if python 2.7? This is probably more a question for Benjamin but doing
> sonmight provide better predictability and "customer service" to our users. I
> might like
