Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/Developer Guidelines"
< OSEE
m (Developer Guidelines moved to OSEE/Developer Guidelines) |
|||
Line 1: | Line 1: | ||
− | + | = Setup = | |
+ | |||
+ | == Code Quality Tools == | ||
+ | |||
+ | |||
+ | == Monitor OSEE Bugs using Mylyn == | ||
+ | |||
+ | [['''Integrating OSEE and Bugzilla''']] | ||
+ | |||
+ | = Before Committing Any Code = | ||
+ | |||
+ | # Synchronize and Update | ||
+ | # Run Code Quality Checks | ||
+ | # Ensure all the tests are green. (Tests projects can be identified by their '*.test' suffix. All tests have to be executed as plug-in unit tests.) | ||
+ | # Ensure the reference documentation is up to date (i.e. reflects your changes) (Documentation is maintained in project 'via the OSEE wiki'). | ||
+ | |||
[[Category:OSEE]] | [[Category:OSEE]] |
Revision as of 13:15, 23 July 2009
Contents
Setup
Code Quality Tools
Monitor OSEE Bugs using Mylyn
'''Integrating OSEE and Bugzilla'''
Before Committing Any Code
- Synchronize and Update
- Run Code Quality Checks
- Ensure all the tests are green. (Tests projects can be identified by their '*.test' suffix. All tests have to be executed as plug-in unit tests.)
- Ensure the reference documentation is up to date (i.e. reflects your changes) (Documentation is maintained in project 'via the OSEE wiki').