[Python-Dev] sprints and pushes
Simon Cross
hodgestar+pythondev at gmail.com
Wed Mar 23 22:27:49 CET 2011
More information about the Python-Dev mailing list
Wed Mar 23 22:27:49 CET 2011
- Previous message: [Python-Dev] sprints and pushes
- Next message: [Python-Dev] sprints and pushes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Mar 23, 2011 at 7:24 PM, Antoine Pitrou <solipsis at pitrou.net> wrote: > On Wed, 23 Mar 2011 10:25:01 -0700 > Ethan Furman <ethan at stoneleaf.us> wrote: >> >> I think the use-case has been lost. Think sprints and multiple push >> races. No one is arguing that the smoke-test should be the default, but >> seriously, are you willing to spend an hour or more re-running the >> complete suite of tests six, eight, or 12 times because of push races in >> a sprint? I can see losing a good portion of your sprinting day. Our sprint model has been to set up a throw-away sprint repository somewhere accessible (github, bitbucket, wherever) and have everyone commit madly to it however they want. Afterwards a few brace souls take the result and commit it to the master repository in a more orderly fashion.
- Previous message: [Python-Dev] sprints and pushes
- Next message: [Python-Dev] sprints and pushes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list