DSDP/MTJ/Proposal for Code Checkin
In addition to all of the requirements for code checkin in the Eclipse process Development Conventions and Guidelines we should follow the following addtional guidelines.
- All code checkins should have a bug as a reference for the code change.
- Each bug should adress a single concept.
- A bug can have multiple checkins to address the issue.
- An exception for small spelling or formatting changes is allowed.
- All checkins should have comments attached to the checkin when it is committed to the CVS archive.
- All checkins should include the bug number at the beginning of the checkin comment. For example, prefix the comment with "Bug xxxxx: "
- The comment should describe the changes.
- The comment should not say 'small change', 'sync code', or something similar.
- All files modified should have their copyright statements updated, if necessary.
- If the file has not been checked in this year, there should be a year update.
- If desired, the additional contributors line should be updated.
- If the copyright has a single entity, and you are not from that entity, you should add the line 'and others' to the copyright statement.
- All code should be checked to make sure that it has been localized and internationalized using the 'external strings' selection in the IDE.
- Any new plug-ins should conform to the Eclipse legal requirements, such as having an about.html.