This page is obsolete and is here for historical reasons. Please refer to Getting Pd Source for up-to-date information.
ready to switch?
i have set up an svn server at puredata.info, e.g. see https://svn.puredata.info/svnroot/gem /unused)
we could still use sourceforge's svn
are we ready to switch?
main structure:
the /branches/ and /tags/ should be only used for:
- releases (incl. maintenance)
- legacy projects (discontinued)
- projects to-be-discontinued (e.g. when you want to try something out): i would even have an
/experimental/meta-branch to handle this
i would propose a layout like:
/trunk/pd/ /trunk/pd-devel/ /trunk/desiredata/ /trunk/externals/ /trunk/extensions/ /trunk/packages/ /trunk/scripts/ /trunk/doc/
note that there is no abstractions section anymore (this is in externals)
procedure
timeline
+ 4.feb-6.feb: creating migration scripts + tests.
+ 7.feb: "day of switch"; do the actual migration; on this day no development activity should be made, as changes might be lost otherwise.
migrationscript
cvs2svn -s puredata-svn --retain-conflicting-attic-files --symbol-default=branch pure-data/
reorganisation
will be done afterwards, once the subversion is running at sourceforge in small incremental steps
- part1: move all the tags/branches into subfolders (e.g.
/tags/v0-38-0/should really become/tags/pd/v0-38-0) - part2: reorganize stuff to your own liking (within the limited scope of "your" subdirectory)