Page History

Introduction

Wiki MarkupGenerally, we coordinate the overall flow on the SpamAssassin-Users and SpamAssassin-Dev [MailingLists]. Then, for specific new functionality or rules, a \[http://bugzilla.spamassassin.org/ 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.unmigrated-wiki-markup

The code itself is maintained in a \[http://subversion.tigris.org/ Subversion\] repository which can be browsed via the following methods:

• HTTP at http://svn.apache.org/repos/asf/spamassassin/
• WebDAV at webdav://svn.apache.org/repos/asf/spamassassin/unmigrated-wiki-markup
• a web UI on SVN history via this \[http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/?root=Apache-SVN ViewCVS view\]unmigrated-wiki-markup
• \[http://svn.apache.org/snapshots/spamassassin/ periodic snapshot tarballs\]. \\
  

General stuff

• UsingBugzilla: What to watch out for when using SpamAssassin's bug tracker.
• DevBookmarks: some good bookmarks for SA developers and contributors.
• NextRelease: Might contain a schedule for the next release.
• VotingProcedure: We follow the ASF way of doing things like this.
• ReleasePolicy (draft): We follow the ASF way here too.
• DevelopmentMode: The difference between C-T-R and R-T-C, etc.
• ProjectRoles: Users, Contributors, Committers, PMC members
• SecurityPolicy: what happens when someone finds a vulnerability in SA
• ContinuousTesting: our continuous testing system
  

...

• BayesStopList: information about the default Bayes "words to skip", and how they were chosen
• MailManglingInTheField: Information about known ways a mail message can be changed in transit.unmigrated-wiki-markup
• \[http://spamassassin.apache.org/publiccorpus/ The SpamAsassin public corpus\]: an old collection of hand-filtered ham and spam for testing GA work, developing new filter techniques, and benchmarking filters.unmigrated-wiki-markup
• \[http://spamassassin.apache.org/gtube/ GTUBE\]: the Generic Test For Unsolicited Bulk Email.
• Package Building: RPM's, etc.
  

...