>>> I think the use-case has been lost. Think sprints and multiple push
>>> races.
Tres> That doesn't work so well at a sprint, where the point is to
Tres> maximize the value of precious face-time to get stuff done *now*.
How about everybody pushes (without testing, or with, at most, Barry's smoke
test) to a sprint-specific local repository? One or more buildbots (or
similar) can just churn away running unit tests from that repository. When
a problem is encountered, the people resposible are going to be right there.
They don't have to slow down their mad hacking until there is a problem.
Since there will be a fair amount of communication between sprinters, the
odds of something bad and horribly hard to fix should be low. Pushes to the
global repository from that sprint repository can happen at a more leisurely
pace and be coordinated manually. Say, everybody breaks for {morning snack,
lunch, dinner}. When they return from the break if the local buildbots are
green you push out to cpython, then everyone starts banging on their
keyboards again.
Skip
_______________________________________________
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
