Updated 1.3.0 Milestone Project Page (markdown)

1.3.0-Milestone-Project-Page.md

@@ -12,29 +12,30 @@
 
 Rather than deleting and re-creating every container on every invocation of `docker-compose up`, Compose will intelligently only re-create what is necessary in order to pick up changes to `docker-compose.yml` or updated service images.
 
-#### Support new Docker networking idioms
-
-Docker 1.7 will introduce the top-level concept of a "network", accompanied by new CLI and API functionality. Compose will add support for networks, which might involve one or both of:
-
-- putting all containers in a project-wide network
-- adding a `network` key so that users can enable more specific inter-service communication
+- [ ] Only recreate what's changed - [#1399](https://github.com/docker/compose/pull/1399)
 
 #### Use labels to keep track of containers
 
 Rather than using container names, which forces Compose to use rather hacky logic in places and stops users from customising names, Compose will use Docker's new "labels" feature to keep track of its containers. This will also improve performance on hosts or clusters with lots of containers running.
 
+- [ ] Use labels instead of names to identify containers - [#1356](https://github.com/docker/compose/pull/1356)
+
 #### Support for labels
 
 Users can add custom metadata to containers with a `labels` configuration option in `docker-compose.yml`.
 
-- [ ] Implement `labels` option - [#1145](https://github.com/docker/compose/pull/1145) (needs re-submitting)
+- [x] Implement `labels` option - [#1145](https://github.com/docker/compose/pull/1145)
 
 
 ### Sprint Goals
 ***
 
-#### Sprint 15 
-_(27 Apr 2015 - 8 May 2015)_
+#### Sprint 16 
+_(11 May 2015 - 22 May 2015)_
+
+- Finish off state convergence
+- Finish off labels for container tracking
+- Investigate testing Compose against Swarm
 
 ### Tracking
 ***