An integration freeze of Feb 1 for most libraries is fine, but to
ensure
we actually ship the AS in Feb I think we should shoot for an earlier
cutoff for core stuff like MC/VDF/VFS/ProfileService. I'd be a lot more
comfortable with January 15 for those. Even earlier if possible.
Ales, you mentioned on another thread today that you thought MC 2.2
would be ready in a week or so. Could you commit to a January 8 date for
getting it into AS trunk?
Yes, that's doable.