Home Original page

[python-committers] improving our code quality [my summary of the "PQM" thread]

Barry Warsaw barry at python.org
Thu Aug 14 20:21:09 CEST 2008 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Aug 14, 2008, at 2:06 PM, Brett Cannon wrote:

> But I honestly think this discussion should wait until after we go
> final with 2.6/3.0. Once that happens and we are all not running
> around trying to get a release out, then we should start from the
> ground up and re-evaluate what we need to change. That includes the
> workflow in the issue tracker, how the buildbots are used, what our
> expected best practices are, cleaning up the test suite, how serious
> we are about moving to a distributed VCS, whether we want a PQM, do we
> want code reviews, etc. But I really think we should be putting the
> time in now to b3 and working towards hitting final before we delve
> into this lengthy conversation.

Thanks for the nice summary Brett.  I completely agree with you that  
any changes in process should happen after 2.6/3.0.  I'll now go back  
to harassing people old skool. :)

- -Barry

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

iQCVAwUBSKR3lXEjvBPtnXfVAQLA2AQAkQZHoL4YH8Di+hKzq3nVdJXazSJPL1Va
5xFnobMmrjKYnvfIK1N50Vg/9pSzxLXVvU1OMYsJdoUnXq1NXaleBIfJbjdMtck5
9CULBncXnokD6IioUI410xhJIXsn/39Xw2INVGiO9GwHy9Y9NlkaEs7xvh8uOkP0
yC8P8+Phu6s=
=/bFZ
-----END PGP SIGNATURE-----
More information about the python-committers mailing list