[Python-Dev] Mercurial?

Dirkjan Ochtman dirkjan at ochtman.nl
Mon Apr 6 11:41:30 CEST 2009

On Mon, Apr 6, 2009 at 11:14, Philippe Fremy <phil at freehackers.org> wrote:
> This is a problem I have with my daily usage of mercurial. It's supposed
> to be great to work offline and to commit your intermediate versions
> before it's fully working but if you do that, all those intermediate non
> working versions find their way into the main repository.

Well, it can also be nice to have smaller commits. They're easier to
review, and will provide easier history to browse/read later on.

BTW, having smaller commits doesn't necessarily equate having
non-working changesets. I.e. in my work on Mercurial, I'll often push
small changesets (we all do), but we try to keep the test suite
passing in every single one of them.

> This means that something like "all test pass 100% or close on every
> version of the repository" is not really feasible unless every committer
> agrees not to have any version in his local repository that does not
> break any tests. Which defeats part of the purpose of being able to have
> a local repository, no ?

This is why you'd want something like a pushlog, to provide a way to
see what revisions were actually tested by buildbots.

Another thing that I discussed with Georg last night would be a setup
where changesets get pushed to a gateway repo that runs the tests and
only pushes to an "official" repo if everything's still green. That
should probably be a topic discussed separately, though.



More information about the Python-Dev mailing list