-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Apr 6, 2009, at 7:55 AM, Michael Foord wrote: > Gated checkins can work fine but can also have many problems. For > example if we have a spuriously failing test then if you are working > on an unrelated issue it will be entirely up to chance as to whether > you can checkin... > > Building the docs would be another thing we could check, although it > can take a while. > > If we have a queue then it could be the case that you do a commit - > and then discover half an hour later that it conflicts with > something that was ahead of you in the queue. All very true. Where I've worked with gated branches, there are procedures for dealing with each of these issues. For a test suite like Python's which runs in a few minutes, I don't think some of the more extreme approaches are necessary (as opposed to a system where a full test run takes *hours*). On the whole though, it's a net win because you know the main tree is always good. This is especially useful around release time! But I guess it's up to Benjamin now to push for that :). Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSdn+iXEjvBPtnXfVAQIEKAP/b3RcUIxcxOpTGfk8POAj+oQXvcvIpI+H 6sN2CWss7bt9qLVlJMFCJoEH78JKnydHuGy+JmZf2rMtnfwIr0w7EFSMoT8X7tPg YflsHn3ePrBddqD9EOwXo+hQfgodSKHEyPHDPgYSMUtiR4TTqkVXD/o4ViQk4K1b YFtRkehHKfc= =F39k -----END PGP SIGNATURE-----
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4