From bce0849e7e8e13d97b42cecb104b0cab50664105 Mon Sep 17 00:00:00 2001 From: Amy Lindburg Date: Thu, 19 Mar 2015 11:51:09 -0700 Subject: [PATCH] Created 1.2.0 Milestone Project Page (markdown) --- 1.2.0-Milestone-Project-Page.md | 37 +++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 1.2.0-Milestone-Project-Page.md diff --git a/1.2.0-Milestone-Project-Page.md b/1.2.0-Milestone-Project-Page.md new file mode 100644 index 0000000..fbe6e23 --- /dev/null +++ b/1.2.0-Milestone-Project-Page.md @@ -0,0 +1,37 @@ +### Schedule + +*** +| Date | Item | +|--------|----| +| 03/22/2015 | Code Freeze; first Release Candidate | +| 04/07/2015 | Release | + +### Tracking + +*** +* [1.2.0 Waffle Board](https://waffle.io/docker/compose?milestone=1.2.0) + +### Release Goals + +*** + +### Extending services + +Services can share configuration using the `extends` keyword, which can be used to factor out common configuration between apps or configure the same app for multiple environments. + +- [ ] `extends` - #1088 + +### Better Swarm integration + +When using Compose with a Swarm cluster, containers that are dependent on one another (e.g. through `links`, `volumes_from` or `net: container`) are scheduled on the same host, meaning most apps will now work out of the box. + +- [x] Make Swarm schedule containers on the same node when they are linked together - #972 + +### Use Docker labels + +Compose uses Docker 1.6's new labels feature to keep track of containers, rather than relying on container names as a source of truth. This is more reliable and allows for container names to be customized. + +- [ ] Specify project and service with container labels - #1066 + + +*** \ No newline at end of file