[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-dev
Subject:    Re: [Python-Dev] [Python-3000]  Code freeze?
From:       Barry Warsaw <barry () python ! org>
Date:       2008-02-29 19:33:34
Message-ID: 079EC957-A3D3-48F9-8A77-A8BEB402E749 () python ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Feb 29, 2008, at 1:59 PM, Stephen J. Turnbull wrote:

> I think that it probably is desirable to to put that deadline pressure
> on.  Individuals who rush to get their work in, and cause alpha-to-
> alpha regressions, can be advised to wait in the future in similar
> circumstances.  Once the rhythm is established, people can expect that
> alphas will be consistently increasing in features and consistently
> decreasing in defects.  If that's not true, something's wrong with the
> process, and the team needs to step back and do something about it.

I agree, and what I already think is broken about our process is that  
changes can land that break the buildbots.  Ideally, this should never  
happen, but our build/test environment has two flaws.  First, it's  
retroactive not proactive.  Second, the tests themselves are not  
always stable.

Given the wide range of platforms and the volunteer nature of the  
buildbot farm, I don't think there's much right now that we can do  
about the second point.  We can do things to mitigate it though, such  
as take a majority-success approach, or give more weight to more  
stable platforms and buildbots.

The second one is tougher because more work on the process is  
necessary, and it would change our workflow for committing changes to  
the tree.  Even with its faults, I'm a big fan of PQM <https://launchpad.net/pqm 
 > though that's not something I think we're ready for.  The bigger  
question though is whether we as a development community would change  
the way we work so that nothing lands if it doesn't pass all the  
tests.  We'd be trading some inconvenience (and administrative  
headaches) for better overall quality and always-releasable guarantees.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iQCVAwUBR8heD3EjvBPtnXfVAQIj/gP/dyf1oavy7y4gTrKHi+j/m+0y4DJstIDf
Fh2MhqExWtCX6V8M3mOn46uRwStwtz9+TUEznNEC8xsxq734GtVyi9Vw6cLpmZQ6
uQp+IBT+nkqNz3sDd8N/ewAGPBO5Ml2m+yn+rfi2XaT5Vfi5akSR/aDwJKGC71fL
8IaWHo5XKEM=
=JQMb
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]