Hi Steven, On 21 January 2015 at 13:00, Steven Jackson <stevenjackson...@gmail.com> wrote: > Am I right in assuming that I should checkout "default," make my own branch, > write failing test cases, make the test cases succeed (occasionally merging > in default) and then...
Yes, you're right up to here :-) The point is that you should commit often, in your own branch; by "often" I mean for example after you have added one or a few tests, after you fixed one of them, and so on. In more details, what you should do is make an account on bitbucket, then go to https://bitbucket.org/pypy/pypy/ and click "fork" (left icons). You get a fork of the repository, e.g. in https://bitbucket.org/yourname/pypy. Then you clone that locally (it takes time) with "hg clone https://bitbucket.org/yourname/pypy";. Make a branch with e.g. "hg branch numpy-sorting". Edit stuff, and "hg commit" regularly; a one-line checkin message is fine. Remember to do "hg push" to publish your commits back to https://bitbucket.org/yourname/pypy, which you should do regularly too, e.g. after every commit or group of commits. The final step is to open a pull request, so that we know that you'd like to merge that branch back to the original pypy/pypy repo (which can also be done several times if you have interesting intermediate states). And if at this point you feel safe working with "hg", we can give you access to pypy/pypy where you can directly push your work; if it is done in branches there is no risk to break stuff and we can still review the branches you want to merge. A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
