Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SpamAssassin: commits

[Spamassassin Wiki] Update of "DevelopmentStuff" by Mark Martinec

 

 

SpamAssassin commits RSS feed   Index | Next | Previous | View Threaded


wikidiffs at apache

Nov 2, 2009, 4:14 AM

Post #1 of 2 (123 views)
Permalink
[Spamassassin Wiki] Update of "DevelopmentStuff" by Mark Martinec

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The "DevelopmentStuff" page has been changed by Mark Martinec.
http://wiki.apache.org/spamassassin/DevelopmentStuff?action=diff&rev1=32&rev2=33

--------------------------------------------------

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/
- * svn checkout https://svn.apache.org/repos/asf/spamassassin/trunk
+ * {{{svn checkout https://svn.apache.org/repos/asf/spamassassin/trunk}}}
* WebDAV at webdav://svn.apache.org/repos/asf/spamassassin/
* a web UI on SVN history via this [[http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/?root=Apache-SVN|ViewCVS view]]
* [[http://svn.apache.org/snapshots/spamassassin/|periodic snapshot tarballs]].


wikidiffs at apache

Nov 2, 2009, 4:16 AM

Post #2 of 2 (105 views)
Permalink
[Spamassassin Wiki] Update of "DevelopmentStuff" by Mark Martinec [In reply to]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The "DevelopmentStuff" page has been changed by Mark Martinec.
http://wiki.apache.org/spamassassin/DevelopmentStuff?action=diff&rev1=33&rev2=34

--------------------------------------------------

== Introduction ==

- Generally, we coordinate the overall flow on the Spam''''''Assassin-Users and Spam''''''Assassin-Dev MailingLists.
+ Generally, 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.

SpamAssassin commits RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.