The OpenSees source code is now stored using Apache Subversion (SVN) software. SVN provides the means to store not only the current version of a piece of source code, but a record of all changes (and who made those changes) that have occurred to that source code. Use of SVN is particularly common on projects with multiple developers, since SVN ensures changes made by one developer are not accidentally removed when another developer posts their changes to the source tree.

Anyone can check out the code via anonymous SVN access, but only certain people have the ability to check in. Those people, basically, are people who I trust not mess up the code. Read our document on hacking OpenSees to find out how to get the ability to check in and how programmers without this ability can check in their code.

For those wanting to obtain source code for a previous release of OpenSees, the release tags for some recent releases are included in the changeLog.



Anonymous SVN Access

This project can be checked out through anonymous access with the following command (use the dos prompt if on a windows machine).

svn co svn://peera.berkeley.edu/usr/local/svn/OpenSees/trunk OpenSees

If you wish to check out a secific version you need to specify the release tag (found on changeLog.). EXAMPLE, to obtain the source code for version 2.4.2, relase tag 5540 you would use the following:

svn co -r 5540 svn://peera.berkeley.edu/usr/local/svn/OpenSees/trunk OpenSees

Users of Windows machines are encouraged to look at TortoiseSVN