[Python-3000] [Python-Dev] Code freeze?
barry at python.org
Fri Feb 29 20:33:34 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
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
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
More information about the Python-3000