Page History
...
Also, 'dspace/branches' are generally used for bug fix releases (e.g. 1.6.1, 1.6.2, etc.). The 'dspace/trunk' is generally used for the next major release (e.g. 1.7, 1.8, etc.). Obviously, if something is a 1.6.0 bug fix, it should be committed both to 'branches/dspace-1_6_x/' and to 'trunk' so that the bug is fixed for both 1.6.1 and 1.7.
How to change your working copy so you can actually commit to SVN:
It is likely you already have a read-only checkout of dspace_trunk, if so, you can change that to a read/write checkout. From the command line, you can just type:
Code Block |
---|
cd [working copy]
svn switch --relocate http://scm.dspace.org/svn/repo/dspace/trunk https://scm.dspace.org/svn/repo/dspace/trunk
|
If you're using an IDE, there is likely a way to svn switch --relocate in your IDE, here's how to svn switch with relocate in Eclipse. However, you may have just as much luck using svn switch with the command line version of SVN.
IRC Overview
- If you can, try to join our DSpace Developer Meetings in #duraspace IRC. It's a good way to stay "in the loop". It's also a good way to get to know everyone. If you cannot make the meeting, transcripts are also available on the above wiki page and off of http://irclogs.duraspace.org/.
...