Re: [matplotlib-devel] switch to subversion repository

[Andrew S. <str...@as...>]

John Hunter wrote:

>>>>>>"Andrew" == Andrew Straw <str...@as...> writes:
>>>>>>            
>>>>>>
>
>    Andrew> Hi All, It looks like SourceForge has (finally) adopted
>    Andrew> site-wide subversion repositories:
>    Andrew> http://sourceforge.net/docs/E09/
>
>    Andrew> What do people feel about migrating from CVS to svn?
>
>I'm +20 on this.  I've complained about sourceforge CVS for a long
>time, mainly because of the lag which in the past could be days, but
>also because of the lack of proper directory management.  Every time
>we wanted to reorganize the directories we would lose history.
>
>If you (or anyone else) want to have a go at migration, please do.  It
>should be pretty easy because we have a pretty simple CVS setup, no
>branches etc.  
>  
>
Great! I'm unable to do it myself (I lack admin rights), but hopefully
someone else can follow the directions on that page. Or else someone can
give me commit rights (astraw@sf) and I'll do it, probably tomorrow
afternoon. Obviously, we should announce in advance when the changeover
will happen.

I propose the following structure, which we could implement as the first
commits of the subversion repository once the CVS data is installed.

matplotlib/ (top level)
    branches/ (empty for now)
    trunk/
        setup.py
        lib/
        (and so on)

This will make life easier down the track when we want to make branches
and will allow checkouts of just the trunk with:
svn co https://svn.sourceforge.net/svnroot/matplotlib/trunk matplotlib

I just downloaded inkscape from SF via svn, and all apparently went
well. So, I'm optimistic on SF's subversion implementation.