Getting the Code
From Ingres Community Wiki
Links to all Ingres downloads (both commercial and open source editions) can be found on this page.
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. We've been told it takes roughly 40 minutes in the UK.)
Please read the README.txt file in the root directory. This will explain how to build.
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 of the road for contributing code to Ingres.
To test your change doesn't break anything:
Run the Test Suite
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 open a ticket for a task to set up a new account in Trac.
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 the SVNGuide.