Page History

...

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/

• Wiki Markup
  a web UI on SVN history via this \[http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/?root=Apache-SVN ViewCVS view\]

...

• Wiki Markup

...

• \[http://svn.apache.org/snapshots/spamassassin/ periodic

...

• snapshot tarballs\]

...

• . \\

General stuff

• RuleDevelopment: some notes on rule development.
• UsingBugzilla: What to watch out for when using SpamAssassin's bug tracker.
• DevBookmarks: some good bookmarks for SA developers and contributors.
• CodingStyle: To be written.
• NextRelease: Might contain a schedule for the next release.
• DownloadFromSvn: How to download the latest version of SpamAssassin from Subversion.
• 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
• ContinuousTesting: our continuous testing system
  

...