From dc02cc882bf93de324791b6a2d54eb250533f6f7 Mon Sep 17 00:00:00 2001
From: nejucomo <>
Date: Sat, 23 Aug 2014 20:41:30 +0000
Subject: [PATCH] Add How to Contribute a Buildbot crosslink.

[Imported from Trac: page BuildbotPolicy, version 8]
---
 BuildbotPolicy.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/BuildbotPolicy.md b/BuildbotPolicy.md
index cbc974d..6752ba7 100644
--- a/BuildbotPolicy.md
+++ b/BuildbotPolicy.md
@@ -1,3 +1,5 @@
+This page is the Tahoe-LAFS project's policy on supported platforms and their relationship to Buildbot slaves.  You may also be interested in [How to Contribute a Buildbot](HowtoContributeABuildbot).
+
 There are two classes of builder for the [Tahoe Buildbot](http://allmydata.org/buildbot/): *Supported* and *Unsupported*.  The buildbot policy has two parts:
 
 1.  Packages are produced for *any* platform only when *all* of the supported platforms pass tests.  This means that if, for example, the Windows platform starts failing unit tests, then we stop producing new .deb packages for Debian or Ubuntu.  Also vice versa: if one of the Supported debian platforms fails its unit tests, then we stop producing new Windows packages.