Update blueprints.

wiki/src/blueprint/evaluate_Docker.mdwn

@@ -6,22 +6,20 @@ For the detailed plans and things to evaluate in Docker, see [[!tails_ticket 753
 Availability on target platforms
 ================================
 
-(as of 20141130)
+(as of 20150120)
 
 Primary target platforms:
 
 * Debian Wheezy: no, even in backports; installation is [possible
   using ugly methods](https://docs.docker.com/installation/debian/)
-* Debian Jessie: 1.3.1~dfsg1-2, and an unblock request has been filed
-  to let 1.3.2 in
-* Debian sid: 1.3.2~dfsg1-1
+* Debian Jessie: 1.3.3~dfsg1-2
+* Debian sid: 1.3.3~dfsg1-2
 * Ubuntu 14.04 LTS: 0.9.1, with 1.0.1 available in trusty-updates
 * Ubuntu 14.10: 1.2.0
 
 Bonus:
 
-* Arch: 1.3.2
-* Fedora: 1.3.0 flagged as stable, 1.3.2 in testing
+* Arch: 1.4.1
 
 Random notes
 ============

wiki/src/blueprint/replace_vagrant.mdwn

@@ -11,9 +11,10 @@ Goals of our Vagrant thing
 2. Improve consistency between our various ways of building Tails ISOs
    (Tails developers currently use at least 3 different build setups,
    and our auto-builder yet another one).
-3. Ideally, our "easy build" instructions should work at least on:
+3. Our "easy build" instructions must work at least on:
    - Debian stable + backports
    - Debian testing
+4. Ideally, our "easy build" instructions should also work at least on:
    - latest Ubuntu LTS
    - latest Ubuntu non-LTS
 
@@ -38,7 +39,7 @@ What we have
   - retrieve the build artifacts from the build VM onto the host system
 
 * Vagrant hasn't been actively maintained in Debian for a while.
-  It'll likely be part of Jessie, but that's by a very short margin.
+  It'll be part of Jessie, but that was by a very short margin.
 
 * VirtualBox vs. QEMU/KVM:
   - One can't run both VirtualBox and QEMU/KVM on the same system.