...
This section of the wiki is intended to hold notes on SpamAssassin's infrastructure – mailing lists, svn, where to ask about getting stuff fixed, etc. The intended audience is the SpamAssassin committers. Hopefully most of this page will be simply links to pages in http://www.apache.org/dev/ , rather than duplicating too much of that site.
Reporting
...
Failures
http://issues.apache.org/jira/ is the bug-tracker used to report and track ASF infrastructure issues. There's no need to report anything if .
Before reporting an issue, check http://status.apache.org/ which replaced http://monitoring.apache.org/status/ lists it as failed, btw in May 1014.
In some cases, you can also mail infrastructure /at/ apache.org. there's a batch There are a number of mailing lists for ASF infrastructure management, see . See http://www.apache.org/dev/infra-mail.html for more information.
Machines we use
http://www.apache.org/dev/machines.html lists the ASF's machines. We use:
minotaur aka people: for publishing releases according to build/README (in svn); spamassassin.apache.org static content - This information is likely out of date but the build/README is accurate.
NOTE: Accounts for minotaur are for committers only – requested via the PMC chair.
SUFFERED CATASTROPHIC FAILURE April 2014: spamassassin.zones.apache.org: a Solaris Zone running on gaea.apache.org, running various services, see SpamAssassinAsfZone
spamassassin-vm.apache.org: A CentOS VM that replaced the Solaris spamassassin.zones.apache.org. This box has the same IP as spamassassin.zones.apache.org as a secondary IP address.
spamassassin2.zones.apache.org: a Solaris Zone running on odyne.apache.org, running various services, see SpamAssassinAsfZone
...