Code Workflow

Drupal Commerce code begins at the level of discussion. Before digging in to do serious module development, ideas are kicked around in IRC and the Brainstorming forums for due consideration. When the objectives are reasonably clear, a functional specification is produced to guide development, along with any necessary notes on how to implement the features or craft the APIs. These specs are themselves turned into issues in the issue tracker where development can be monitored.

When a developer is ready to get to work, he or she should chime in on the appropriate issue on d.o and get up to speed with current development. Instead of developing primarily through CVS on d.o, we're using GitHub to aid in collaborative development. Developers should refer to our GitHub documentation to see how to get plugged in and push code back upstream for consideration in the main Drupal Commerce repository.

Once code is committed to the main repository, it will be committed into CVS on d.o as well. We'll still be using CVS there to tag releases, and anyone not comfortable with Git can still checkout the code from CVS and patch against it. We'll have documentation soon to coach developers through getting started with Git, and in the meantime you can refer to this SVN -> Git tutorial.

Bugs should always be reported via the issue tracker on d.o, but feature requests should start here in the forums so they can be worked into the specification. The specification here should always be an up to date representation of what we have in code.