On Fri, Feb 18, 2011 at 4:53 PM, John Hunter <jdh2...@gmail.com> wrote: > I have removed everyone's commit access to the mpl svn server in > advance of the github migration, which is underway. Darren will reply > when github is live. > > svn is dead, long live github!
I just pushed the repositories up to github.com/matplotlib . A few notes: * Jarrod offered to contribute to the docs to describe the recommended workflow. For the impatient: - Visit https://github.com/matplotlib/matplotlib and hit the "fork" button - clone the resulting repository, eg "git clone g...@github.com:username/matplotlib.git" - make a new branch (git checkout -b new_feature) and hack away - don't merge upstream changes into your feature branch (it makes the history graph look ugly) - when you are ready to have your changes merged upstream, push your branch to your own repository at github - switch to that branch in your github profile, and select the "pull request" button. This starts the code review process, which also gives others a chance to inspect the git history graph before it gets merged into the official mpl repo. * python-3 support should happen in the matploltib-py3 repo, the master branch in that repository contains Michael's changes from the py3k svn branch, but rebased on top of the more recent changes to the master branch in the main matplotlib repo. Darren ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
