updated roadmap and philosophy

philosophy.md

@@ -6,7 +6,7 @@ We value collaboration, transparency, and fairness in everything we do.
 
 We also think the following are true:
 
-* Container versioning (i.e. versioning both images and configuration) will become increasingly important over the next year as more people use containers in production, just as versioning services has become common practice. 
+* Deployment versioning (i.e. versioning both images and configuration) will become increasingly important over the next year as more people use containers in production, just as versioning services has become common practice. 
 * Software development is a multi-player game played with single player tools. Better collaborative tooling needs to be built for software organizations.
 * Introducing proprietary software into your infrastructure introduces external market risk into your product, and this risk should be very carefully considered whenever evaluating options. [See more of our thoughts on this](https://medium.com/@ciaomack/parsegate-the-case-against-proprietary-infrastructure-d397a89cbb2b).
 

roadmap.md

@@ -1,30 +1,35 @@
-###spread roadmap
+###Spread roadmap
 ---
 
-This is a high level roadmap for spread development. The dates below should not be considered authoritative, but rather indicative of a projected timeline for spread. 
+This is a high level roadmap for spread development. The dates below should not be considered authoritative, but rather indicative of a projected timeline for Spread. 
 
 ####Feb. 2016
 
 * `spread deploy`: One command deploy to a remote Kubernetes cluster
 	* Including building Docker context with deployment
-	* `spread deploy -p`: Pushes all images to registry, even those not built by `spread deploy`.
 	* Handle updates for all Kubernetes objects
 
 ####Mar. 2016
 
-* Logging and debugging
-	* `spread debug`: Returns the current spread version, Kubernetes version, Docker version, Go version, computer operating system, the Kubernetes config, spread config, and the content and timestamp of last command ran
-	* `spread logs`: Returns logs for any deployment, automatic trying until logs are accessible.
 * Support for local development with Kubernetes
-	* Easy setup of local cluster
-	* Cluster-to-cluster syncing
+	* Easy setup of local cluster: see <a href="https://github.com/redspread/localkube">Localkube</a>
+* Support for Linux and Windows
+
+####April 2016
+
+* Kubernetes configuration versioning
+	* See our prototype: <a href="https://github.com/redspread/kit">Kit</a>
+
+####May 2016
+
+* Inner-app linking
+* Easy rollbacks
+* Local development
 	* `spread build`: Builds Docker context and pushes to a local Kubernetes cluster.
 	* `spread status`: Prints information about the state of the project
-* Inner-app linking
-* Support for Linux and Windows
 
-####Apr. 2016
+####June 2016
 
-* Container versioning
-	* Version the image + configuration of containers 
-	* `spread rewind`: Quickly rollback to a previous deployment.
+* Logging and debugging
+	* `spread debug`: Returns the current spread version, Kubernetes version, Docker version, Go version, computer operating system, the Kubernetes config, spread config, and the content and timestamp of last command ran
+	* `spread logs`: Returns logs for any deployment, automatic trying until logs are accessible.