summaryrefslogtreecommitdiff
path: root/development.md
diff options
context:
space:
mode:
authorDaniel Smith <dbsmith@google.com>2015-07-13 17:13:09 -0700
committerDaniel Smith <dbsmith@google.com>2015-07-13 17:48:40 -0700
commitb8889dc9532b5b58504d8b0ab52df2d5c386e449 (patch)
tree26c079dac82595dee7877228641f52df61e85497 /development.md
parent37813afc4bc36b2f617cdac0233e1d02b45352eb (diff)
Apply mungedocs changes
Diffstat (limited to 'development.md')
-rw-r--r--development.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/development.md b/development.md
index 157f49d6..ba9b9897 100644
--- a/development.md
+++ b/development.md
@@ -281,8 +281,8 @@ go run hack/e2e.go -v -ctl='delete pod foobar'
## Conformance testing
End-to-end testing, as described above, is for [development
-distributions](../../docs/devel/writing-a-getting-started-guide.md). A conformance test is used on
-a [versioned distro](../../docs/devel/writing-a-getting-started-guide.md).
+distributions](writing-a-getting-started-guide.md). A conformance test is used on
+a [versioned distro](writing-a-getting-started-guide.md).
The conformance test runs a subset of the e2e-tests against a manually-created cluster. It does not
require support for up/push/down and other operations. To run a conformance test, you need to know the
@@ -300,4 +300,6 @@ hack/run-gendocs.sh
```
+<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/devel/development.md?pixel)]()
+<!-- END MUNGE: GENERATED_ANALYTICS -->