DerbyCommitHowTo: Committing patches to the Derby Subversion Repository
DerbySnapshotOrRelease: guidelines for doing a Derby snapshot or release
MoveAChangeBetweenBranches: Some tips for moving a fix from one branch to another.
HowToBackOutaChange: Instructions on how a committer can back out a change.
DocumentationDevelopment: How the docs are built and maintained.
Edit a commit message for revision N in svn's log svn propedit --revprop -r N svn:log
AccessingOlderSnapshots: How to retrieve an older snapshot if needed for testing
HowToRunJiraVtiReports: How to run reports against Jira using the demo VTI.
Accessing the Source or Docs via Subversion
The code and docs are stored in Subversion. You can find out the exact URL to a particular part of the repository by browsing to it, for example by starting at https://svn.apache.org/repos/asf/db/derby/ in a web browser. This is also a useful way to get to know the structure of our repository (the same repository is shared for all parts of the Derby project that is under version control).
For browsing the actual contents of the files in the repository, and for examining what was done when, by whom and in which checkins, you can use ViewVC, at http://svn.apache.org/viewvc/db/derby/.
When you set up your subversion client, there are a few configuration steps which help. Check the main Apache page at http://www.apache.org/dev/version-control.html#https-svn-config for details. Note that the file extensions used in the Derby documentation aren't covered by the default Apache file (from the above link), and that we do mention to add these on http://db.apache.org/derby/manuals/dita.html