Test Development Process

Test Development Process

 The following set of steps will help the sponsors to integrate externally contributed code to STC gates. For now, this process presumes that external contributors will actively seek how to contribute the code back.

1. Make sure the external developer has signed the Oracle Contributor Agreement

 2. Review the code/idea to make sure it's a valid contribution.

 3. File any bugs or RFEs to track the code as needed. Mention that external contributor is working on the CR in the CR itself.

 4. Create a webrev of the code, and have it reviewed.
 This is usually done via the testing-discuss-AT-opensolaris.org mailing list in the open after the webrev of the changes is uploaded to cr.opensolaris.org.
 Normally external developers don't do the Portions copyright for minor changes but if the file in question was contributed as a whole or significantly rewritten then it could contain the copyright, for example:

# Portions Copyright 2008 Erik Trauschke

 This should be preferably located under the Oracle copyright.

 5. Test the code.

 6. File an STC webRTI. The OCA (Oracle Contributor Agreement) number should be included in the RTI. The external contributor should be mentioned in the putback comments. The putback comments could look e.g. like this:

6754842 extended port list specification needs to be tested
Code contributed by Erik Trauschke <erik.trauschke@...>

 Note: the mail address was truncated to protect the contributor from spam.

 7. Integrate the code after getting approval from CRT advocate.