Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OSEE/Developer Guidelines"
< OSEE
(→Monitor OSEE Bugs using Mylyn) |
|||
| Line 6: | Line 6: | ||
== Monitor OSEE Bugs using Mylyn == | == Monitor OSEE Bugs using Mylyn == | ||
| − | [[ | + | [[Integrating OSEE and Bugzilla]] |
= Before Committing Any Code = | = Before Committing Any Code = | ||
Revision as of 13:16, 23 July 2009
Contents
Setup
Code Quality Tools
Monitor OSEE Bugs using Mylyn
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').