Introduction

Generally, we coordinate the overall flow on the SpamAssassin-Users and SpamAssassin-Dev MailingLists. Then, for specific new functionality or rules, a Bugzilla bug should be created to track progress and provide a forum for discussion; any patches should be stored (as an attachment) on that Bugzilla bug.

By using a Bugzilla bug to track code changes, we have an easy way to find the discussion/timeline of that functionality's development at any point in the future, since we can simply say "see bug 2134 for details/discussion/arguments" etc.

The code itself is maintained in a Subversion repository which can be browsed via the following methods:

General stuff

Patches and Coding

Rule Development

Infrastructure

Stuff about scoring

More Stuff

Historical information relating to the Incubation process


CategoryDevelopment

DevelopmentStuff (last edited 2011-11-22 20:39:38 by Darxus)