One time set up:
Complete the Ingres contributors agreement and mail/fax/email it to Ingres.
Request your account by opening a ticket against the "new account" component. Please include your full name and email address.
Pulling code is trivial:
svn co http://code.ingres.com/ingres/main <place you want to put the code> e.g. svn co http://code.ingres.com/ingres/main ~/code
(the time will depend on your internet access for typical cable/DSL - 3.0 Mbps download, it takes around 10 minutes)
For each update you do:
Please create a ticket in trac to track the change. You'll be using this ticket number as the reason when committing.
Please pre-review the approach with the architect or subject matter expert for the area. Once you secure their approval, you can begin work.
To make a code change:
edit the file you wish to change as you would normally svn status - to show what you've modified
Please review the rules we follow to accept/reject code.
To test your change doesn't break anything:
More details coming soon.
PLEASE NOTE: You're quite welcome to stop here if this gives you what you want. If you would like to provide the change back to Ingres, you must have provided us with the Ingres Contributors agreement. Also, you will not be able to commit without an account and proper privilege. Please see new users for details.
To code inspect:
More details coming soon.
To commit the change back to the repository:
svn commit -m <ticket> --username <userid> - to submit the changes back to SvN. You can commit a file at a time, or everything in your workspace.
* The commit message can contain any text and any number of ticket numbers, but you need to put a # before each ticket number. For example "#83 and #95 fixed". This will ensure trac automatically hyperlinks it. (just as it has here)
To maintain your workspace and keep it up to date:
svn update <root of code dir> - to rebase and pull in any new changes since you pulled the code.
(you can update just a file, but that's bad practice... better to stay on baseline with everyone else and update the root directory of your workspace)
For more details about Subversion, please see SVNGuide.
