HOW TO: Developing Milestones PM

General Development Notes

1. Important: before you deploy to a developer org from GitHub, you must be sure that DE has translations enabled.
2. All development should start with your own fork of Milestones-PM. When you have completed development, submit a standard pull request.
3. The same code base is used for Managed and Unmanaged packages. Managed package namespace is LABSMPM. Note: you should not have to hard code this anywhere.
4. All unique names (Apex class, Label full name, Visualforce page, etc) have a Pseudo Namespace: "Milestone1_". Why? This reduces the likelihood of name collision in the unmanaged package.
5. All text is rendered using a Label. Why? This enables Japanese localization.
6. Before submitting, ensure you have scanned your code using http://security.force.com. There should be no issues flagged with this code. NOTE: that this scanner DOES NOT scan code installed as part of a package. You must push code to the scanning org using something other than a package (ANT, the IDE, etc) then scan.
7. Milestones PM CANNOT include changes based on Workflow at this time.