VersionControl

Version Control

All that you do should be checked in, aka committed, to a version control system, usually svn (subversion) for WebSphere Commerce related code. This ensures nothing is lost.

When to Commit

For small bugs and minor UI issues, you can commit and review in a deployed environment (e.g. dev2) before reviewing with a team lead. For layout and larger changes, review your changes with a team lead before committing code.

Check In Comments

Include the following with each check in:

• Ticket number (JIRA, Wrike, etc)
• Brief description of problem & solution or bug fixed

Testing Committed Code

The following environments are available for validating your changes work as expected:

• Dev2
• QA
• BAT

All changes should be tested in at least one of these before it gets to production.