Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/DevelopmentStuff The comment on the change is:
reformat a little, add note about bugzilla, add AboutClas link
------------------------------------------------------------------------------
Generally, we coordinate the overall flow on the Spam''''''Assassin-Users and Spam''''''Assassin-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.
The code itself is maintained in a [
http://subversion.tigris.org/ Subversion] repository which can be browsed via the following methods:
@@ -14, +16 @@
== 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
+
+ == Patches and Coding ==
+
+ * CodingStyle: some tips on how we format our code.
+ * AboutClas: information on the Apache Contributor License Agreement.
+ * DownloadFromSvn: How to download the latest version of SpamAssassin from Subversion.
+
+ == Rule Development ==
+
+ * RuleDevelopment: some notes on rule development.
* ManualRuleUpdates: how to manually put out a rule update
- * BayesStopList: information about the default Bayes "words to skip"
== Infrastructure ==
@@ -43, +51 @@
== More Stuff ==
+ * 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.
* [
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.
* [
http://spamassassin.apache.org/gtube/ GTUBE]: the Generic Test For Unsolicited Bulk Email.