Merge pull request #6028 from xiang90/plat

doc: update platform.md

Documentation/op-guide/supported-platform.md

@@ -4,14 +4,16 @@
 
 The following table lists etcd support status for common architectures and operating systems,
 
-| Architecture | Operating System | Status       |
-| ------------ | ---------------- | ------------ |
-| amd64        | Darwin           | Experimental |
-| amd64        | Linux            | Stable       |
-| amd64        | Windows          | Experimental |
-| arm64        | Linux            | Experimental |
-| arm          | Linux            | Unstable     |
-| 386          | Linux            | Unstable     |
+| Architecture | Operating System | Status       | Maintainers      |
+| ------------ | ---------------- | ------------ | ---------------- |
+| amd64        | Darwin           | Experimental | etcd maintainers | 
+| amd64        | Linux            | Stable       | etcd maintainers |
+| amd64        | Windows          | Experimental |                  |
+| arm64        | Linux            | Experimental | @glevand         |
+| arm          | Linux            | Unstable     |                  |
+| 386          | Linux            | Unstable     |                  |
+
+* etcd-maintainers are listed in https://github.com/coreos/etcd/blob/master/MAINTAINERS.
 
 Experimental platforms appear to work in practice and have some platform specific code in etcd, but do not fully conform to the stable support policy. Unstable platforms have been lightly tested, but less than experimental. Unlisted architecture and operating system pairs are currently unsupported; caveat emptor.
 
@@ -22,7 +24,7 @@ For etcd to officially support a new platform as stable, a few requirements are
 1. An "official" maintainer for the platform with clear motivation; someone must be responsible for taking care of the platform.
 2. Set up CI for build; etcd must compile.
 3. Set up CI for running unit tests; etcd must pass simple tests.
-4. Set up CI for running integration tests; etcd must pass intensive tests.
+4. Set up CI (TravisCI, SemaphoreCI or Jenkins) for running integration tests; etcd must pass intensive tests.
 5. (Optional) Set up a functional testing cluster; an etcd cluster should survive stress testing.
 
 ### 32-bit and other unsupported systems