Preparations for the 1.18.0 release

[Curtis Hovey-Canonical]

I have reorganised the milestones to reflect our intent to release
1.18.0 in the next 9 days.

1. Target bug to 1.17.5 that *must* be in this release. I will not
defer bugs unfixed bugs to the 1.18.0 release.

2. If users like 1.17.5, we will re-release it as 1.18.0

3. I still see regressions that are not fixed. I have targeted them to
1.18.0. I also targeted additional test and doc related bugs to
1.18.0. I think these bug must be fixed to release 1.18.0.

4. We can defer 1.18.0 (or 1.17.5) bugs to 1.20.0 if we agree that do
not affect users who will upgrade from 1.16.6.

5. If we prune the bugs to a very short list. It is possibly that I
will release 1.17.5 in 1 day, then release 1.18.0 2 days later.

6. I think we need to release 1.18.0 before March 21. If one of the
targeted bugs must be fixed by then, but is unlikely to be fixed, we
need to discuss this today and tomorrow.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui