Spreadthunderbird: Difference between revisions

Line 133: Line 133:


== How to develop STB ==
== How to develop STB ==
# Get [[SVN|svn access]] if you don't already
# Request [[SVN|svn access]] if you don't already
# Get a bug to work on
# Find a bug to work on
# Write code for the bug
# Fix the bug
# If the bug fixes a problem with a contributed module on drupal.org then create a patch and submit for review on drupal.org by the module maintainer. As soon as the patch is accepted and the module updated then update the ticket so that the module can be updated on STB. If the bug fixes a problem with bespoke code that is in SVN then create a patch upload to Bugzilla and request a review.Once the patch is accepted, commit to SVN with the bug # in the commit message and a brief description of what the patch does or the bug title. Add a comment to Bugzilla with the revision number of the commit: 'rXXXX'.  
# If the bug fixes a problem with a contributed module on drupal.org then create a patch and submit to the module maintainer for review on its project page on drupal.org. As soon as the patch is accepted and the module updated on drupal.org then update the bug on mozilla.org with the name of the module and the tag attached to the new release so that the module can be updated on Spreadthunderbird. If the bug fixes a problem with bespoke code that is in SVN on mozilla.org then create a patch upload to Bugzilla and request a review by Gozer. Once the patch has been reviewed/accepted, commit to SVN with the bug # in the commit message and a brief description of what the patch does or the bug title. Add a comment to Bugzilla with the revision number of the commit: 'rXXXX'.  
# Mark the bug as fixed
# Mark the bug as fixed
# QA verifies bug and marks as VERIFIED if it's really been fixed
# QA verifies bug and marks as VERIFIED if it's really been fixed
Confirmed users
884

edits