Le mercredi 02 février 2011 à 11:47 -0500, Barry Warsaw a écrit : > >One issue it raises is the difficulties caused by freezing the trunk for > >releases. Instead they advocate creating the release branch at the point of > >the release candidate instead of freezing trunk. There are issues I > >currently *can't* work on because trunk is frozen and would personally prefer > >to see us use the branch-on-release-candidate process. > > This is one of the primary problems solved by a dvcs. You can *always* and > *easily* work on new features, publish them for comment and review by others, > make continual progress regardless of the release status of the official > branches, and easily track movement in those official branches.
I am already using a DVCS (git-svn) to work on Python, especially for my work on Unicode. It is just impossible to work on an huge change on trunk, it changes too fast. A SVN branch should be created or a DVCS tool should be used. I prefer DVCS over SVN: it's faster, it's easier to do small commits, merge/remove commits, etc. But my last problem is that I don't know how to publish my DVCS repository. It would be possible to host it at home, but I am to lazy to setup my server for that. The problem is also that the repository is huge (254 MB): publish it to Internet would be slow (I upload at 80 KB/sec) if I have to publish all files (and the history) the first time. It would be faster if I can fork an existing repository on a server (download is always faster than upload). I suppose that bitbucket will have a miror of Python (because they already proposed to host the official repository), and so it will be trivial to fork Python repository with just a bitbucket account. That will be great, because it will easier to share a branch, without having to be a Python core developer. We might also host forks on our server, but it implies to have to manager user accounts (with permissions), so do the same job than Bitbucket and other hosting websites. I don't use Mercurial miror today, because I cannot be used to commit into Subversion (if I'm wrong, please tell me how to do that!), and I'm also using git-svn to commit into Python. Victor _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
