Rules of the road for contributing code to Ingres

Changes provided without the contributors agreement in place will be rejected.

No pre-approval on the approach will be less likely to be accepted in a timely manner.

Items already fixed will be rejected (obviously).

Constrain your update to fixing issues within one area or the same issue across areas

Ensure you use functions provided in the CL rather than the functions they abstract.

Updates contributed with no test plans will be rejected.

Updates without history comments describing the change and why it was made will be rejected.

Unrelated code cleanup as part of other updates will be rejected.

Please do not remove items from the revision history.

No profanity or unprofessional comments please.

Really large changes are less likely to be approved. (ensure there's pre-approval)

Updates fixing many bugs, or features with the same update will be rejected.

Changes that infringe intellectual property rights without permission will be rejected.

Changes that introduce unwarranted duplication of code/functions will be rejected.

Changes that violate the architecture model will be rejected.

Updates that cause handsoffqa (test suite) diffs will be rejected.