Hi All, It looks like SourceForge has (finally) adopted
> site-wide subversion repositories:
> http://sourceforge.net/docs/E09/
> 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.
JDH
John Hunter wrote:
"Andrew" == Andrew Straw <strawman@...36...> writes:
> Hi All, It looks like SourceForge has (finally) adopted
> site-wide subversion repositories:
> http://sourceforge.net/docs/E09/
> 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@...325...) 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 matplotlib download | SourceForge.net matplotlib
I just downloaded inkscape from SF via svn, and all apparently went
well. So, I'm optimistic on SF's subversion implementation.
What about tags?
tags/
0.87
0.87.1
0.88
...
···
On Mon, Feb 27, 2006 at 09:45:34AM -0800, Andrew Straw wrote:
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)
--
albert chin (china@...319...)
Albert Chin wrote:
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)
What about tags?
tags/
0.87
0.87.1
0.88
...
Yes, tags, too.
I've gone ahead and created a test subversion repository on my local
machine. Everything looks OK. It looks like the new checkout string to
get matplotlib (and not toolkits, htdocs, and users_guide) would be
something like "svn co path.to - a really cool domain parked on Park.io trunk/matplotlib matplotlib".
You probably don't want to check out the tags directory -- 3.4 are
generated on your disk then!
Here's the top-level layout created directly by cvs2svn. Sorry I didn't
have time to format this nicely.
astraw@...326...:~/tmp/MPL/svn_co/mpl.svn$ ls
branches tags trunk
astraw@...326...:~/tmp/MPL/svn_co/mpl.svn$ ls branches/
jdhunter vendor
astraw@...326...:~/tmp/MPL/svn_co/mpl.svn$ ls tags/
basemap_v0_1_1 v0_2_1 v0_4_2 v0_61 v0_62_2 v0_7 v0_8 v0_86_2
post_numerix v0_3 v0_4_3 v0_6_1 v0_62_3 v0_70 v0_80 v0_87
pre_numerix v0_3_1 v0_5 v0_61_0 v0_62_4 v0_71 v0_8_1
release-0-1 v0_3_2 v0_5_1 v0_6_1b v0_63_0 v0_7_1 v0_82
start v0_3_3 v0_5_2 v0_6_2 v0_64 v0_72 v0_83_2
v0_1_2 v0_4 v0_6 v0_62_0 v0_65 v0_73 v0_86
v0_2 v0_4_1 v0_60_2 v0_62_1 v0_65_1 v0_74 v0_86_1
astraw@...326...:~/tmp/MPL/svn_co/mpl.svn$ ls trunk/
course CVSROOT htdocs matplotlib toolkits users_guide
astraw@...326...:~/tmp/MPL/svn_co/mpl.svn$ ls trunk/matplotlib/
agg23 examples KNOWN_BUGS MANIFEST setupext.py
API_CHANGES fonts lib MANIFEST.in setup.py
boilerplate.py images license matplotlibrc.template src
CHANGELOG __init__.py license.py NUMARRAY_ISSUES swig
CXX INSTALL Makefile README TODO
DEVNOTES INTERACTIVE makeswig.py setupegg.py unit
···
On Mon, Feb 27, 2006 at 09:45:34AM -0800, Andrew Straw wrote: