Using iODBC Open Source Edition GIT Tree

Introduction

Developers who want to actively track progress of the iODBC source code and contribute bugfixes or enhancements to the project need Git access.

This access requires basic knowledge of Git itself; the general layout of open source and GNU projects; the use of autoconf and automake; and other things that are beyond the scope of this document.

Git Archive Server Access

GitHub?

For main development, we publish the iODBC open-source tree to GitHub. We encourage everyone who is interested in tracking the project to create an account there.

Users who mainly just want to look at the code can use the GitHub web interface or check out a local copy of the tree:


$ git clone git://github.com/openlink/iODBC.git

At this point, you can create your own work branch based on any available branch; create bug fixes; commit them to your own branch; and then use git format-patch to generate diffs.

Developers are encouraged to fork the project on GitHub?, create branches for enhancements and bug fixes, and submit pull requests so changes can be reviewed and incorporated into the main tree for future release.

For more information, see GitHub Documentation.

SourceForge?

OpenLink? continues to use SourceForge to release source tarballs and certain binaries.

SourceForge? also contains a frozen CVS archive for historical reference, and read-only Git archive access is available there as well.

For more information, see SourceForge Git Documentation.

Git Tag-Signing Key

To verify signed releases, import our Git public GPG key in one of these ways:

Further Documentation

Please see our Git Usage document concerning the usage of branches and tags.

For an introduction to Git, see the Git Quickstart and Tips guide.