[Python-Dev] sprints and pushes
Antoine Pitrou
solipsis at pitrou.net
Wed Mar 23 18:24:00 CET 2011
More information about the Python-Dev mailing list
Wed Mar 23 18:24:00 CET 2011
- Previous message: [Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost - committed, pulled, merged, what is "collapse"?)
- Next message: [Python-Dev] sprints and pushes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Well, keep in ming hg is a *distributed* version control system. You don't have to push your changes right now. You can keep your changesets for yourself, make several of them (different bug fixes, for example), and push them (after a single merge) at the end of day. Regards Antoine.
- Previous message: [Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost - committed, pulled, merged, what is "collapse"?)
- Next message: [Python-Dev] sprints and pushes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list