Am 19.11.2010 15:36, schrieb "Martin v. Löwis": >> - date Hg will be available for write access (it should be frozen for >> a while, to give the folks doing the conversion a chance to make sure >> buildbot is back up and run, commit emails are working properly, etc) > > I would target the build slaves to the Mercurial repository already in > the testing phase, e.g by creating builders for building from commits > to the 3k branch. I hope Buildbot supports multiple change sources now. > Likewise, I'd also see commit emails being delivered in the test phase > already, and let committers make test commits to trigger this all (and > also to get acquainted with the Mercurial tools they are going to use, > without fear of breaking something).
I've already let my Mercurial buildbot configuration run for a few checkins while testing it; a separate changesource was not needed. The commit email hook also has been tested extensively by its usage for the distutils2 repo, which are also sent to python-checkins. That said, it will of course be nice to activate both for the test repo as well, once it's available. Georg _______________________________________________ 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/archive%40mail-archive.com
